From: Johannes Altmanninger <aclopte@gmail.com>
To: util-linux@vger.kernel.org
Cc: Johannes Altmanninger <aclopte@gmail.com>
Subject: [PATCH 2/4] mount.8.adoc: use bold font for literal text in synopsis
Date: Sun, 6 Feb 2022 07:11:56 +0100 [thread overview]
Message-ID: <20220206061158.752262-2-aclopte@gmail.com> (raw)
In-Reply-To: <20220206061158.752262-1-aclopte@gmail.com>
In a synopsis, *bold* text means "type exactly as shown" (see man(1)).
mount.8.adoc has *--make*-[*shared*|...] which is weird because
the middle dash is not in bold even though it's meant to be typed
literally. Make it bold like the surrounding text.
Signed-off-by: Johannes Altmanninger <aclopte@gmail.com>
---
sys-utils/mount.8.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-utils/mount.8.adoc b/sys-utils/mount.8.adoc
index 6f4465d0d..714b8133d 100644
--- a/sys-utils/mount.8.adoc
+++ b/sys-utils/mount.8.adoc
@@ -55,7 +55,7 @@ mount - mount a filesystem
*mount* *--bind*|*--rbind*|*--move* _olddir newdir_
-*mount* *--make*-[*shared*|*slave*|*private*|*unbindable*|*rshared*|*rslave*|*rprivate*|*runbindable*] _mountpoint_
+*mount* *--make-*[*shared*|*slave*|*private*|*unbindable*|*rshared*|*rslave*|*rprivate*|*runbindable*] _mountpoint_
== DESCRIPTION
--
2.35.1.301.gcdacdcff8b.dirty
next prev parent reply other threads:[~2022-02-06 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 6:11 [PATCH 1/4] newgrp.1.adoc: use bold font for command name in synopsis Johannes Altmanninger
2022-02-06 6:11 ` Johannes Altmanninger [this message]
2022-02-06 6:11 ` [PATCH 3/4] kill.1.adoc: clarify syntax of -SIG argument " Johannes Altmanninger
2022-02-06 6:11 ` [PATCH 4/4] getopt.1.adoc: render synopsis rules on separate lines Johannes Altmanninger
2022-02-07 18:42 ` Mario Blättermann
2022-02-07 10:00 ` [PATCH 1/4] newgrp.1.adoc: use bold font for command name in synopsis Karel Zak
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=20220206061158.752262-2-aclopte@gmail.com \
--to=aclopte@gmail.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;
as well as URLs for NNTP newsgroup(s).