linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Frank A. Kingswood" <frank@kingswood-consulting.co.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: update mkfs.btrfs help info for raid5/6
Date: Sat, 20 Apr 2013 16:48:45 -0700	[thread overview]
Message-ID: <5173295D.4060503@redhat.com> (raw)
In-Reply-To: <51732102.6080104@kingswood-consulting.co.uk>

On 4/20/13 4:13 PM, Frank A. Kingswood wrote:
> On 04/03/13 01:37, zwu.kernel@gmail.com wrote:
>> From: Zhi Yong Wu<wuzhy@linux.vnet.ibm.com>
>>
>>    Since raid5/6 support was introduced, we should update mkfs.btrfs help info.
>>
>> Signed-off-by: Zhi Yong Wu<wuzhy@linux.vnet.ibm.com>
>> ---
>>   mkfs.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mkfs.c b/mkfs.c
>> index 5ece186..f9f26a5 100644
>> --- a/mkfs.c
>> +++ b/mkfs.c
>> @@ -326,7 +326,7 @@ static void print_usage(void)
>>       fprintf(stderr, "options:\n");
>>       fprintf(stderr, "\t -A --alloc-start the offset to start the FS\n");
>>       fprintf(stderr, "\t -b --byte-count total number of bytes in the FS\n");
>> -    fprintf(stderr, "\t -d --data data profile, raid0, raid1, raid10, dup or single\n");
>> +    fprintf(stderr, "\t -d --data data profile, raid0, raid1, raid5, raid6, raid10, dup or single\n");
>>       fprintf(stderr, "\t -l --leafsize size of btree leaves\n");
>>       fprintf(stderr, "\t -L --label set a label\n");
>>       fprintf(stderr, "\t -m --metadata metadata profile, values like data profile\n");
> 
> Nitpick: that line of output is now longer than 80. Perhaps instead of "\t " have a few spaces at the start of each line.

or maybe:

+    fprintf(stderr, "\t -d --data data profile: [raid0|raid1|raid5|raid6|raid10|dup|single]\n");

I think that fits...

> Frank
> 
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2013-04-20 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  1:37 [PATCH] btrfs-progs: update mkfs.btrfs help info for raid5/6 zwu.kernel
2013-04-20 23:13 ` Frank A. Kingswood
2013-04-20 23:48   ` Eric Sandeen [this message]
     [not found]     ` <CAEH94Lg2b9uYk=+cf_KXKnFYnMxPBM_rKGJairX14TtvGHD=ww@mail.gmail.com>
2013-04-21  9:36       ` Zhi Yong Wu

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=5173295D.4060503@redhat.com \
    --to=sandeen@redhat.com \
    --cc=frank@kingswood-consulting.co.uk \
    --cc=linux-btrfs@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).