From: Eric Sandeen <sandeen@redhat.com>
To: Chris Frost <chris@frostnet.net>
Cc: linux-ext4@vger.kernel.org
Subject: [PATCH V2] mke2fs.8.in: clarify the sign of a block-size constraint.
Date: Thu, 29 Jul 2010 11:59:42 -0500 [thread overview]
Message-ID: <4C51B37E.4020404@redhat.com> (raw)
In-Reply-To: <20100724220124.GO4032@pooh.frostnet.net>
This bit of the mke2fs manpage is slightly confusing:
-b block-size
Specify the size of blocks in bytes. <snip>
If block-size is negative, then mke2fs will use heuristics
to determine the appropriate block size, with the constraint
that the block size will be at least block-size bytes.
because it sounds like the block size will be at least a negative
number. Clarify just what the negative sign means.
Reported-by: Chris Frost <chris@frostnet.net>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/misc/mke2fs.8.in b/misc/mke2fs.8.in
index 45a99f8..b46e7e2 100644
--- a/misc/mke2fs.8.in
+++ b/misc/mke2fs.8.in
@@ -173,7 +173,7 @@ the expected usage of the filesystem (see the
.B \-T
option). If
.I block-size
-is negative, then
+is preceded by a negative sign ('-'), then
.B mke2fs
will use heuristics to determine the
appropriate block size, with the constraint that the block size will be
next prev parent reply other threads:[~2010-07-29 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 22:01 [PATCH] mke2fs.8.in: correct the sign of a block-size constraint Chris Frost
2010-07-25 4:55 ` Eric Sandeen
2010-07-29 4:11 ` Chris Frost
2010-07-29 16:59 ` Eric Sandeen [this message]
2010-07-31 0:40 ` [PATCH V2] mke2fs.8.in: clarify " Ted Ts'o
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=4C51B37E.4020404@redhat.com \
--to=sandeen@redhat.com \
--cc=chris@frostnet.net \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.