From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: David Sterba <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 3/6] btrfs-progs: fi usage, update manpage
Date: Fri, 19 Dec 2014 14:04:56 +0900 [thread overview]
Message-ID: <5493B1F8.2070106@jp.fujitsu.com> (raw)
In-Reply-To: <488c53a0e5e255f9504cfc2a029e7c1c72994f66.1418912740.git.dsterba@suse.cz>
Hi David,
On 2014/12/18 23:27, David Sterba wrote:
> Signed-off-by: David Sterba <dsterba@suse.cz>
> ---
> Documentation/btrfs-filesystem.txt | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/Documentation/btrfs-filesystem.txt b/Documentation/btrfs-filesystem.txt
> index a8f2972a0e1a..85a94eb52569 100644
> --- a/Documentation/btrfs-filesystem.txt
> +++ b/Documentation/btrfs-filesystem.txt
> @@ -123,6 +123,34 @@ Show or update the label of a filesystem.
> If a newlabel optional argument is passed, the label is changed.
> NOTE: the maximum allowable length shall be less than 256 chars
>
> +*usage* [options] <path> [<path>...]::
> +Show detailed information about internal filesystem usage.
Options from "-b" to "-t" are the completely same as "btrfs fi df"'s ones.
So how about pointing the df's options as follows?
===============================================================================
...
+
`Options`
+
-T::::
Show data in tabular format
+
There are some option to set unit. See description of *df*'s options
from '-b' to '-t'.
+
If conflicting options are passed, the last one takes precedence.
...
===============================================================================
I consider it can prevent mistakes caused by further changes.
Thanks,
Satoru
> ++
> +`Options`
> ++
> +-b|--raw::::
> +raw numbers in bytes, without the 'B' suffix
> +-h::::
> +print human friendly numbers, base 1024, this is the default
> +-H::::
> +print human friendly numbers, base 1000
> +--iec::::
> +select the 1024 base for the following options, according to the IEC standard
> +--si::::
> +select the 1000 base for the following options, according to the SI standard
> +-k|--kbytes::::
> +show sizes in KiB, or kB with --si
> +-m|--mbytes::::
> +show sizes in MiB, or MB with --si
> +-g|--gbytes::::
> +show sizes in GiB, or GB with --si
> +-t|--tbytes::::
> +show sizes in TiB, or TB with --si
> +-T::::
> +show data in tabular format
> +
> +If conflicting options are passed, the last one takes precedence.
> +
> EXIT STATUS
> -----------
> *btrfs filesystem* returns a zero exit status if it succeeds. Non zero is
>
next prev parent reply other threads:[~2014-12-19 5:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 14:27 [PATCH 0/6] Btrfs-progs, add units to 'usage' subcommands David Sterba
2014-12-18 14:27 ` [PATCH 1/6] btrfs-progs: fi usage, change option for tabular output to T David Sterba
2014-12-18 14:27 ` [PATCH 2/6] btrfs-progs: fi usage, add switches to set output units David Sterba
2014-12-18 14:27 ` [PATCH 3/6] btrfs-progs: fi usage, update manpage David Sterba
2014-12-19 5:04 ` Satoru Takeuchi [this message]
2014-12-19 9:56 ` Satoru Takeuchi
2014-12-19 13:36 ` David Sterba
2014-12-21 23:25 ` Satoru Takeuchi
2014-12-18 14:27 ` [PATCH 4/6] btrfs-progs: dev usage, add switches to set output units David Sterba
2014-12-18 14:27 ` [PATCH 5/6] btrfs-progs: dev usage, update manpage David Sterba
2014-12-18 14:28 ` [PATCH 6/6] btrfs-progs: unify unit mode parameters and variables David Sterba
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=5493B1F8.2070106@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--cc=dsterba@suse.cz \
--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 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.