linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: dsterba@suse.cz
Cc: Fan Chengniang <fancn.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 RESEND] btrfs-progs: make btrfs qgroups show human readable sizes
Date: Wed, 14 Jan 2015 23:20:29 +0500	[thread overview]
Message-ID: <20150114232029.04bb3bec@natsu> (raw)
In-Reply-To: <20150114154633.GU3685@twin.jikos.cz>

On Wed, 14 Jan 2015 16:46:33 +0100
David Sterba <dsterba@suse.cz> wrote:

> On Tue, Jan 13, 2015 at 01:53:39PM +0800, Fan Chengniang wrote:
> > make btrfs qgroups show human readable sizes
> > using --human-readable option, example:
> 
> That's too long to type and the idea was to add all the long options
> that force the specific unit base, ie. --kbytes/--mbytes/..., --raw,
> --si and --iec. We can possibly make the human readable the default
> because that's what I'd expect to see to have a quick overview and can
> use the other options otherwise.
> 
> The geopt parser accepts short options if they're unique, so --kb or
> even --k works as a very convenient shorcut for frequent commandline
> use.

FWIW both of the GNU coreutils "df" and "ls" use the "-h, --human-readable"
combination of options. Also the human-readable sizes are not the default format with those.
Why not follow the rule of the least surprise and just adopt the same behavior?

-- 
With respect,
Roman

  reply	other threads:[~2015-01-14 18:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13  5:53 [PATCH v2 RESEND] btrfs-progs: make btrfs qgroups show human readable sizes Fan Chengniang
2015-01-14 15:46 ` David Sterba
2015-01-14 18:20   ` Roman Mamedov [this message]
2015-01-15 12:02     ` David Sterba
2015-01-15  1:01   ` Qu Wenruo
2015-01-15 12:05     ` David Sterba
2015-01-15 20:41       ` btrfs command completion Was: " Duncan
2015-01-15  1:17   ` Fan Chengniang/樊成酿
2015-01-15 12:30     ` David Sterba
2015-01-15 13:50       ` 樊成酿

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=20150114232029.04bb3bec@natsu \
    --to=rm@romanrm.net \
    --cc=dsterba@suse.cz \
    --cc=fancn.fnst@cn.fujitsu.com \
    --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).