From: Benno Schulenberg <bensberg@telfort.nl>
To: util-linux@vger.kernel.org
Subject: [PATCH 10/11] mkfs.cramfs: (man) mark arguments of -N and -l in bold, not italics
Date: Tue, 25 Mar 2025 11:43:04 +0100 [thread overview]
Message-ID: <20250325104305.23980-10-bensberg@telfort.nl> (raw)
In-Reply-To: <20250325104305.23980-1-bensberg@telfort.nl>
Those possible arguments are literal values, not placeholder words.
Also, improve the description of option -l.
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
---
disk-utils/mkfs.cramfs.8.adoc | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/disk-utils/mkfs.cramfs.8.adoc b/disk-utils/mkfs.cramfs.8.adoc
index 56e5065b9..5c6b1f971 100644
--- a/disk-utils/mkfs.cramfs.8.adoc
+++ b/disk-utils/mkfs.cramfs.8.adoc
@@ -44,8 +44,8 @@ Use defined block size, which has to be divisible by page size.
*-e* _edition_::
Use defined file system edition number in superblock.
-*-N* _big, little, host_::
-Use defined endianness. Value defaults to _host_.
+*-N* *big*|*little*|*host*::
+Use the specified endianness. The default is *host*.
*-i* _file_::
Insert a _file_ to cramfs file system.
@@ -63,12 +63,12 @@ This option is ignored. Originally the *-s* turned on directory entry sorting.
Make explicit holes.
*-l*[**=**_mode_]::
- Use exclusive BSD lock for device or file it operates. The optional argument
- _mode_ can be _yes_, _no_ (or 1 and 0) or _nonblock_. If the _mode_
- argument is omitted, it defaults to _"yes"_. This option overwrites
- environment variable *$LOCK_BLOCK_DEVICE*. The default is not to use any
- lock at all, but it's recommended to avoid collisions with udevd or other
- tools.
+Use an exclusive BSD lock for the device or file that is operated upon.
+The optional argument _mode_ can be *yes* (*1*), *no* (*0*), or *nonblock*.
+If the _mode_ argument is omitted, it defaults to *yes*.
+This option overrides the environment variable *$LOCK_BLOCK_DEVICE*.
+The default is to not use any lock at all, but using a lock
+is recommended to avoid collisions with udevd or other tools.
include::man-common/help-version.adoc[]
--
2.48.1
next prev parent reply other threads:[~2025-03-25 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 10:42 [PATCH 01/11] ipcrm: move a constant argument in order to gettextize the message Benno Schulenberg
2025-03-25 10:42 ` [PATCH 02/11] ipcrm: in usage text, use two lines when option+arguments is very long Benno Schulenberg
2025-03-25 10:42 ` [PATCH 03/11] ipcutils, lsipc: unabbreviate two words in some error messages Benno Schulenberg
2025-03-25 10:42 ` [PATCH 04/11] chmem: print warnings about failures always (not only with --verbose) Benno Schulenberg
2025-03-25 10:42 ` [PATCH 05/11] chmem: (man) add missing end-of-bold marker, and add missing OR bar Benno Schulenberg
2025-03-25 10:43 ` [PATCH 06/11] fstrim: mark only the mountpoint as placeholder, not options -A and -a Benno Schulenberg
2025-03-25 10:43 ` [PATCH 07/11] swapon: improve a translator hint, and remove a pointless one Benno Schulenberg
2025-03-25 10:43 ` [PATCH 08/11] mkfs.cramfs: reduce the synopsis to the standard, succinct form Benno Schulenberg
2025-03-25 10:43 ` [PATCH 09/11] mkfs.cramfs: vertically align the option descriptions of the usage text Benno Schulenberg
2025-03-25 10:43 ` Benno Schulenberg [this message]
2025-03-25 10:43 ` [PATCH 11/11] ipcs: align the first group of options with later ones in " Benno Schulenberg
2025-03-27 9:54 ` [PATCH 01/11] ipcrm: move a constant argument in order to gettextize the message 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=20250325104305.23980-10-bensberg@telfort.nl \
--to=bensberg@telfort.nl \
--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