From: Goffredo Baroncelli <kreijack@inwind.it>
To: "Hugo Mills" <hugo@carfax.org.uk>,
"Ilya Dryomov" <idryomov@gmail.com>,
linux-btrfs@vger.kernel.org, "Roman Mamedov" <rm@romanrm.ru>,
"Sébastien Maury" <sebastien.maury@inserm.fr>
Subject: Re: [PATCH 1/2] Update btrfs filesystem df command
Date: Wed, 03 Oct 2012 22:53:49 +0200 [thread overview]
Message-ID: <506CA5DD.9000808@inwind.it> (raw)
In-Reply-To: <20121003203852.GE25498@carfax.org.uk>
On 10/03/2012 10:38 PM, Hugo Mills wrote:
>>> + if( !(flags& (DF_SHOW_SUMMARY|DF_SHOW_DETAIL)) ){
>>> > > + fprintf(stderr, "btrfs filesystem df: it is not possible to specify -s AND -d\n");
>> >
>> > This doesn't look right at all. You are adding two switches and
>> > specifying both of them is an error? A little too much for a command
>> > whose job is to do some basic math and pretty-print the result.
>> >
>> > How about displaying just the summary by default and then adding a
>> > *single* switch (-v or whatever) for summary+details?
> I'd prefer to see both sections by default. The reason for this is
> that without both sections, people tend to get confused because they
> don't know they're looking at half the story (e.g. some numbers change
> twice as fast as they think they should).
I agree with Hugo. As default both the section should be showed.
> I think supplying both options should probably show both sections
> again, and make it not an error to do so, but I'm happy either way.
Because the default is to show both the sections, passing a switch means
"hide the other section". So passing both the switches means: "hide both
the sections"...
This is the reason of the check.
I am thinking to remove both the switches... But today is too late...
Now I am seeing a reply by Ilya which reached this same conclusion...
But today is still to late. Tomorrow I will rearrange the patch...
>
> Hugo.
Goffredp
next prev parent reply other threads:[~2012-10-03 20:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 17:22 [PATCH][BTRFS-PROGS][V2] btrfs filesystem df Goffredo Baroncelli
2012-10-03 17:22 ` [PATCH 1/2] Update btrfs filesystem df command Goffredo Baroncelli
2012-10-03 20:34 ` Ilya Dryomov
2012-10-03 20:38 ` Hugo Mills
2012-10-03 20:43 ` Ilya Dryomov
2012-10-03 20:53 ` Goffredo Baroncelli [this message]
2012-10-03 17:22 ` [PATCH 2/2] Update help page Goffredo Baroncelli
2012-10-03 19:32 ` [PATCH][BTRFS-PROGS][V2] btrfs filesystem df David Sterba
2012-10-03 19:38 ` Goffredo Baroncelli
2012-10-04 7:15 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2012-10-13 19:14 [PATCH][BTRFS-PROGS][V6] " Goffredo Baroncelli
2012-10-13 19:14 ` [PATCH 1/2] Update btrfs filesystem df command Goffredo Baroncelli
2012-10-13 17:47 [PATCH][BTRFS-PROGS][V4] btrfs filesystem df Goffredo Baroncelli
2012-10-13 17:47 ` [PATCH 1/2] Update btrfs filesystem df command Goffredo Baroncelli
2012-10-04 17:27 [PATCH][BTRFS-PROGS][V3] btrfs filesystem df Goffredo Baroncelli
2012-10-04 17:27 ` [PATCH 1/2] Update btrfs filesystem df command Goffredo Baroncelli
2012-10-03 11:43 [PATCH][BTRFS-PROGS][V1] btrfs filesystem df Goffredo Baroncelli
2012-10-03 11:43 ` [PATCH 1/2] Update btrfs filesystem df command Goffredo Baroncelli
2012-10-03 15:02 ` Ilya Dryomov
2012-10-03 16:34 ` Goffredo Baroncelli
2012-10-03 17:20 ` Ilya Dryomov
2012-10-03 17:38 ` Goffredo Baroncelli
2012-10-03 17:09 ` Goffredo Baroncelli
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=506CA5DD.9000808@inwind.it \
--to=kreijack@inwind.it \
--cc=hugo@carfax.org.uk \
--cc=idryomov@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.ru \
--cc=sebastien.maury@inserm.fr \
/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.