Blame SOURCES/0003-Use-comments-to-separate-sections-in-manual-pages.patch

3540f1
From 93763f99bb8404f17b177eb7cd62e7c6e8fdc14e Mon Sep 17 00:00:00 2001
3540f1
From: Jean Delvare <jdelvare@suse.de>
3540f1
Date: Tue, 29 Jan 2019 14:11:46 +0100
3540f1
Subject: [PATCH 03/11] Use comments to separate sections in manual pages
3540f1
3540f1
Blank lines are interpreted as actual blank lines in manual pages.
3540f1
Use comments instead to visually separate sections. Otherwise an
3540f1
extra blank like is inserted before every section.
3540f1
3540f1
Signed-off-by: Jean Delvare <jdelvare@suse.de>
3540f1
---
3540f1
 man/biosdecode.8 | 11 ++++++++---
3540f1
 man/dmidecode.8  | 18 +++++++++++-------
3540f1
 man/ownership.8  | 10 +++++++---
3540f1
 man/vpddecode.8  | 12 +++++++-----
3540f1
 4 files changed, 33 insertions(+), 18 deletions(-)
3540f1
3540f1
diff --git a/man/biosdecode.8 b/man/biosdecode.8
3540f1
index a96eb681c136..cf7d4db01249 100644
3540f1
--- a/man/biosdecode.8
3540f1
+++ b/man/biosdecode.8
3540f1
@@ -1,10 +1,12 @@
3540f1
 .TH BIOSDECODE 8 "February 2007" "dmidecode"
3540f1
+.\"
3540f1
 .SH NAME
3540f1
 biosdecode \- \s-1BIOS\s0 information decoder
3540f1
+.\"
3540f1
 .SH SYNOPSIS
3540f1
 .B biosdecode
3540f1
 .RB [ OPTIONS ]
3540f1
-
3540f1
+.\"
3540f1
 .SH DESCRIPTION
3540f1
 .B biosdecode
3540f1
 parses the \s-1BIOS\s0 memory and prints information about all structures (or
3540f1
@@ -54,7 +56,7 @@ started its life as a part of
3540f1
 .B dmidecode
3540f1
 but as more entry point types were added, it was moved to a different
3540f1
 program.
3540f1
-
3540f1
+.\"
3540f1
 .SH OPTIONS
3540f1
 .TP
3540f1
 .BR "-d" ", " "--dev-mem FILE"
3540f1
@@ -68,17 +70,20 @@ Display usage information and exit
3540f1
 .TP
3540f1
 .BR "-V" ", " "--version"
3540f1
 Display the version and exit
3540f1
-
3540f1
+.\"
3540f1
 .SH FILES
3540f1
 .I /dev/mem
3540f1
+.\"
3540f1
 .SH BUGS
3540f1
 Most of the time,
3540f1
 .B biosdecode
3540f1
 prints too much information (you don't really care about addresses)
3540f1
 or not enough (because it doesn't follow pointers and has no lookup
3540f1
 tables).
3540f1
+.\"
3540f1
 .SH AUTHORS
3540f1
 Alan Cox, Jean Delvare
3540f1
+.\"
3540f1
 .SH "SEE ALSO"
3540f1
 .BR dmidecode (8),
3540f1
 .BR mem (4),
3540f1
diff --git a/man/dmidecode.8 b/man/dmidecode.8
3540f1
index 52100a82435e..1f6529d99e91 100644
3540f1
--- a/man/dmidecode.8
3540f1
+++ b/man/dmidecode.8
3540f1
@@ -1,10 +1,12 @@
3540f1
 .TH DMIDECODE 8 "January 2019" "dmidecode"
3540f1
+.\"
3540f1
 .SH NAME
3540f1
 dmidecode \- \s-1DMI\s0 table decoder
3540f1
+.\"
3540f1
 .SH SYNOPSIS
3540f1
 .B dmidecode
3540f1
 .RB [ OPTIONS ]
3540f1
-
3540f1
+.\"
3540f1
 .SH DESCRIPTION
3540f1
 .B dmidecode
3540f1
 is a tool for dumping a computer's \s-1DMI\s0 (some say \s-1SMBIOS\s0) table
3540f1
@@ -58,7 +60,7 @@ displayed value.
3540f1
 Decoded values. The information presented of course depends on the type
3540f1
 of record. Here, we learn about the board's manufacturer, model, version
3540f1
 and serial number.
3540f1
-
3540f1
+.\"
3540f1
 .SH OPTIONS
3540f1
 .TP
3540f1
 .BR "-d" ", " "--dev-mem FILE"
3540f1
@@ -158,10 +160,9 @@ is run on a system with BIOS that boasts new SMBIOS specification, which
3540f1
 is not supported by the tool yet, it will print out relevant message in
3540f1
 addition to requested data on the very top of the output. Thus informs the
3540f1
 output data is not reliable.
3540f1
-
3540f1
+.\"
3540f1
 .SH "DMI TYPES"
3540f1
 The \s-1SMBIOS\s0 specification defines the following \s-1DMI\s0 types:
3540f1
-
3540f1
 .TS
3540f1
 r l
3540f1
 __
3540f1
@@ -246,7 +247,7 @@ dmidecode --type 0,13
3540f1
 dmidecode --type bios
3540f1
 .IP \(bu
3540f1
 dmidecode --type BIOS
3540f1
-
3540f1
+.\"
3540f1
 .SH BINARY DUMP FILE FORMAT
3540f1
 The binary dump files generated by --dump-bin and read using --from-dump
3540f1
 are formatted as follows:
3540f1
@@ -255,7 +256,7 @@ The SMBIOS or DMI entry point is located at offset 0x00.
3540f1
 It is crafted to hard-code the table address at offset 0x20.
3540f1
 .IP \(bu "\w'\(bu'u+1n"
3540f1
 The DMI table is located at offset 0x20.
3540f1
-
3540f1
+.\"
3540f1
 .SH UUID FORMAT
3540f1
 There is some ambiguity about how to interpret the UUID fields prior to SMBIOS
3540f1
 specification version 2.6. There was no mention of byte swapping, and RFC 4122
3540f1
@@ -269,7 +270,7 @@ compatibility, it was decided to interpret the UUID fields according to RFC
3540f1
 4122 (no byte swapping) when the SMBIOS version is older than 2.6, and to
3540f1
 interpret the first 3 fields as little-endian (byte-swapped) when the SMBIOS
3540f1
 version is 2.6 or later. The Linux kernel follows the same logic.
3540f1
-
3540f1
+.\"
3540f1
 .SH FILES
3540f1
 .I /dev/mem
3540f1
 .br
3540f1
@@ -278,11 +279,14 @@ version is 2.6 or later. The Linux kernel follows the same logic.
3540f1
 .br
3540f1
 .I /sys/firmware/dmi/tables/DMI
3540f1
 (Linux only)
3540f1
+.\"
3540f1
 .SH BUGS
3540f1
 More often than not, information contained in the \s-1DMI\s0 tables is inaccurate,
3540f1
 incomplete or simply wrong.
3540f1
+.\"
3540f1
 .SH AUTHORS
3540f1
 Alan Cox, Jean Delvare
3540f1
+.\"
3540f1
 .SH "SEE ALSO"
3540f1
 .BR biosdecode (8),
3540f1
 .BR mem (4),
3540f1
diff --git a/man/ownership.8 b/man/ownership.8
3540f1
index f24ef9437e21..71ed78844081 100644
3540f1
--- a/man/ownership.8
3540f1
+++ b/man/ownership.8
3540f1
@@ -1,10 +1,12 @@
3540f1
 .TH OWNERSHIP 8 "February 2005" "dmidecode"
3540f1
+.\"
3540f1
 .SH NAME
3540f1
 ownership \- Compaq ownership tag retriever
3540f1
+.\"
3540f1
 .SH SYNOPSIS
3540f1
 .B ownership
3540f1
 .RB [ OPTIONS ]
3540f1
-
3540f1
+.\"
3540f1
 .SH DESCRIPTION
3540f1
 .B ownership
3540f1
 retrieves and prints the "ownership tag" that can be set on Compaq
3540f1
@@ -14,7 +16,7 @@ package,
3540f1
 .B ownership
3540f1
 doesn't print any version information, nor labels, but only the raw
3540f1
 ownership tag. This should help its integration in scripts.
3540f1
-
3540f1
+.\"
3540f1
 .SH OPTIONS
3540f1
 .TP
3540f1
 .BR "-d" ", " "--dev-mem FILE"
3540f1
@@ -25,11 +27,13 @@ Display usage information and exit
3540f1
 .TP
3540f1
 .BR "-V" ", " "--version"
3540f1
 Display the version and exit
3540f1
-
3540f1
+.\"
3540f1
 .SH FILES
3540f1
 .I /dev/mem
3540f1
+.\"
3540f1
 .SH AUTHOR
3540f1
 Jean Delvare
3540f1
+.\"
3540f1
 .SH "SEE ALSO"
3540f1
 .BR biosdecode (8),
3540f1
 .BR dmidecode (8),
3540f1
diff --git a/man/vpddecode.8 b/man/vpddecode.8
3540f1
index c9e4acfd2fb9..1cc2b76ce552 100644
3540f1
--- a/man/vpddecode.8
3540f1
+++ b/man/vpddecode.8
3540f1
@@ -1,10 +1,12 @@
3540f1
 .TH VPDDECODE 8 "February 2007" "dmidecode"
3540f1
+.\"
3540f1
 .SH NAME
3540f1
 vpddecode \- \s-1VPD\s0 structure decoder
3540f1
+.\"
3540f1
 .SH SYNOPSIS
3540f1
 .B vpddecode
3540f1
 .RB [ OPTIONS ]
3540f1
-
3540f1
+.\"
3540f1
 .SH DESCRIPTION
3540f1
 .B vpddecode
3540f1
 prints the "vital product data" information that can be found in almost
3540f1
@@ -17,19 +19,17 @@ Box Serial Number
3540f1
 Motherboard Serial Number
3540f1
 .IP \(bu
3540f1
 Machine Type/Model
3540f1
-
3540f1
 .PP
3540f1
 Some systems have these additional items:
3540f1
 .IP \(bu "\w'\(bu'u+1n"
3540f1
 BIOS Release Date
3540f1
 .IP \(bu
3540f1
 Default Flash Image File Name
3540f1
-
3540f1
 .PP
3540f1
 Note that these additional items are not documented by IBM, so this is
3540f1
 guess work, and as such should not be blindly trusted. Feedback about
3540f1
 the accuracy of these labels is welcome.
3540f1
-
3540f1
+.\"
3540f1
 .SH OPTIONS
3540f1
 .TP
3540f1
 .BR "-d" ", " "--dev-mem FILE"
3540f1
@@ -62,11 +62,13 @@ Display usage information and exit
3540f1
 .TP
3540f1
 .BR "-V" ", " "--version"
3540f1
 Display the version and exit
3540f1
-
3540f1
+.\"
3540f1
 .SH FILES
3540f1
 .I /dev/mem
3540f1
+.\"
3540f1
 .SH AUTHOR
3540f1
 Jean Delvare
3540f1
+.\"
3540f1
 .SH "SEE ALSO"
3540f1
 .BR biosdecode (8),
3540f1
 .BR dmidecode (8),
3540f1
-- 
3540f1
2.17.1
3540f1