linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
Cc: dsterba@suse.cz, Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
	takeuchi_satoru@jp.fujitsu.com
Subject: Re: [PATCH v3] btrfs-progs: Documentation: add T/P/E description for resize cmd
Date: Thu, 1 Jan 2015 20:27:55 -0700	[thread overview]
Message-ID: <CAJCQCtSeguD-oC9ikBc-Mn6_xeu2f-EbfLSFLpSOKgVsEs-T5g@mail.gmail.com> (raw)
In-Reply-To: <1419904337-9945-1-git-send-email-guihc.fnst@cn.fujitsu.com>

On Mon, Dec 29, 2014 at 6:52 PM, Gui Hecheng <guihc.fnst@cn.fujitsu.com> wrote:
> Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
> Reviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
> ---
> changelog
>         v1->v2:
>                 s/\'E\'(EiB)/or \'E\'(EiB)/ as suggested by Satoru, thanks.
>         v2->v3:
>                 replace confusing format 'K'(KiB) etc. Thanks, David.
> ---
>  Documentation/btrfs-filesystem.txt | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/btrfs-filesystem.txt b/Documentation/btrfs-filesystem.txt
> index a8f2972..96c4420 100644
> --- a/Documentation/btrfs-filesystem.txt
> +++ b/Documentation/btrfs-filesystem.txt
> @@ -102,8 +102,9 @@ If the prefix + or - is present the size is increased or decreased
>  by the quantity <size>.
>  If no units are specified, the unit of the <size> parameter defaults to
>  bytes. Optionally, the size parameter may be suffixed by one of the following
> -units designators: \'K\', \'M', or \'G', kilobytes, megabytes, or gigabytes,
> -respectively.
> +units designators: \'K\', \'M\', \'G\', \'T\', \'P\', or \'E\', which represent
> +KiB, MiB, GiB, TiB, PiB, or EiB, respectively.
> +
>  +
>  If \'max' is passed, the filesystem will occupy all available space on the
>  device devid.

Small problem with the rendering of this commit
d4ef1a06f8be623ae94e4d498c306e8dd1605bef, when I use 'man btrfs
filesystem' the above portion looks like this:

 'K', 'M', 'G', 'T', 'P', or 'E\',

I'm not sure why there's a trailing slash after the E.

Separately, for -t option, it reads:
For <start>, <len>, <size> it is possible to append a suffix like k
for 1 KBytes, m for 1 MBytes...

So there's a reference of small k and m there, but then later
references for capitalized KMGTPE, so maybe the reference could be
more like e.g. LVM where it's described as [bBsSkKmMgGtTpPeE] and just
omit the sS for sectors since this isn't supported.


-- 
Chris Murphy

  reply	other threads:[~2015-01-02  3:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22  2:01 [PATCH] btrfs-progs: Documentation: add T/P/E description for resize cmd Gui Hecheng
2014-12-22  3:20 ` Satoru Takeuchi
2014-12-22  7:22   ` [PATCH v2] " Gui Hecheng
2014-12-29 16:07     ` David Sterba
2014-12-30  1:23       ` Gui Hecheng
2014-12-30  1:52       ` [PATCH v3] " Gui Hecheng
2015-01-02  3:27         ` Chris Murphy [this message]
2015-01-02 16:12           ` David Sterba
2015-01-02 16:21             ` David Sterba
2015-01-05  1:42               ` Gui Hecheng

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=CAJCQCtSeguD-oC9ikBc-Mn6_xeu2f-EbfLSFLpSOKgVsEs-T5g@mail.gmail.com \
    --to=lists@colorremedies.com \
    --cc=dsterba@suse.cz \
    --cc=guihc.fnst@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=takeuchi_satoru@jp.fujitsu.com \
    /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).