From: Andreas Dilger <adilger@whamcloud.com>
To: tytso@mit.edu, linux-ext4@vger.kernel.org
Cc: Andreas Dilger <adilger@whamcloud.com>
Subject: [PATCH] mke2fs: Document stripe_width, not stripe-width
Date: Wed, 29 Jun 2011 10:47:40 -0600 [thread overview]
Message-ID: <1309366060-25985-1-git-send-email-adilger@whamcloud.com> (raw)
For consistency with other multi-word options, document the extended
option stripe_width instead of stripe-width. This also avoids the
complexity of parsing options that have an embedded '-'.
Signed-off-by: Andreas Dilger <adilger@whamcloud.com>
---
misc/mke2fs.8.in | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/misc/mke2fs.8.in b/misc/mke2fs.8.in
index 0d4b046..6901497 100644
--- a/misc/mke2fs.8.in
+++ b/misc/mke2fs.8.in
@@ -209,7 +209,7 @@ This mostly affects placement of filesystem metadata like bitmaps at
time to avoid placing them on a single disk, which can hurt performance.
It may also be used by the block allocator.
.TP
-.BI stripe-width= stripe-width
+.BI stripe_width= stripe-width
Configure the filesystem for a RAID array with
.I stripe-width
filesystem blocks per stripe. This is typically stride-size * N, where
--
1.7.3.4
next reply other threads:[~2011-06-29 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 16:47 Andreas Dilger [this message]
2011-07-18 3:14 ` [PATCH] mke2fs: Document stripe_width, not stripe-width 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=1309366060-25985-1-git-send-email-adilger@whamcloud.com \
--to=adilger@whamcloud.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).