From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Cc: mtk.manpages@gmail.com
Subject: [PATCH 07/12] Fix formatting errors in page cross references
Date: Thu, 10 Nov 2016 11:59:49 +0100 [thread overview]
Message-ID: <5eca5018-ca00-67a3-1999-8beecba629a9@gmail.com> (raw)
In-Reply-To: <404e11c0-9f88-b460-7398-d00585a9bf16@gmail.com>
These pages had errors such as
.BR page (x) .
which should be
.BR page (x).
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---
disk-utils/swaplabel.8 | 2 +-
misc-utils/findmnt.8 | 2 +-
sys-utils/blkdiscard.8 | 2 +-
sys-utils/dmesg.1 | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/disk-utils/swaplabel.8 b/disk-utils/swaplabel.8
index 45c0492..8bac331 100644
--- a/disk-utils/swaplabel.8
+++ b/disk-utils/swaplabel.8
@@ -53,7 +53,7 @@ will truncate it and print a warning message.
Specify a new \fIUUID\fR for the device.
The \fI UUID\fR
must be in the standard 8-4-4-4-12 character format, such as is output by
-.BR uuidgen (1) .
+.BR uuidgen (1).
.PP
.SH AUTHOR
.B swaplabel
diff --git a/misc-utils/findmnt.8 b/misc-utils/findmnt.8
index 105f2c5..6e4ddb4 100644
--- a/misc-utils/findmnt.8
+++ b/misc-utils/findmnt.8
@@ -162,7 +162,7 @@ or \fB\-\-first\-only\fP options.
The standard columns always use the new version of the information from the
mountinfo file, except the umount action which is based on the original
information cached by
-.BR findmnt (8) .
+.BR findmnt (8).
The poll mode allows to use extra columns:
.RS
.TP
diff --git a/sys-utils/blkdiscard.8 b/sys-utils/blkdiscard.8
index da3d6cb..3b24f2f 100644
--- a/sys-utils/blkdiscard.8
+++ b/sys-utils/blkdiscard.8
@@ -13,7 +13,7 @@ blkdiscard \- discard sectors on a device
.B blkdiscard
is used to discard device sectors. This is useful for solid-state
drivers (SSDs) and thinly-provisioned storage. Unlike
-.BR fstrim (8) ,
+.BR fstrim (8),
this command is used directly on the block device.
.PP
By default,
diff --git a/sys-utils/dmesg.1 b/sys-utils/dmesg.1
index 6e0812f..d553418 100644
--- a/sys-utils/dmesg.1
+++ b/sys-utils/dmesg.1
@@ -120,7 +120,7 @@ Print the raw message buffer, i.e. do not strip the log-level prefixes.
Note that the real raw format depends on the method how
.BR dmesg (1)
reads kernel messages. The /dev/kmsg device uses a different format than
-.BR syslog (2) .
+.BR syslog (2).
For backward compatibility,
.BR dmesg (1)
returns data always in the
--
2.5.5
next prev parent reply other threads:[~2016-11-10 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <404e11c0-9f88-b460-7398-d00585a9bf16@gmail.com>
2016-11-10 10:59 ` [PATCH 04/12] Fix page cross references Michael Kerrisk (man-pages)
2016-11-10 10:59 ` [PATCH 05/12] Fix section number in lockf() page xref Michael Kerrisk (man-pages)
2016-11-10 10:59 ` [PATCH 06/12] Fix reference for scheduling discussion Michael Kerrisk (man-pages)
2016-11-10 10:59 ` Michael Kerrisk (man-pages) [this message]
2016-11-10 10:59 ` [PATCH 08/12] Replace reference to sigvec(2) with sigaction(2) Michael Kerrisk (man-pages)
2016-11-10 10:59 ` [PATCH 09/12] SEE ALSO: add cross reference to namespaces(7) Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5eca5018-ca00-67a3-1999-8beecba629a9@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox