From: David Sterba <dsterba@suse.cz>
To: Anand Jain <Anand.Jain@oracle.com>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org,
chris.mason@fusionio.com, jbacik@fusionio.com
Subject: Re: [PATCH 2/2] btrfs-progs: filesystem show of specified mounted disk should work
Date: Thu, 24 Oct 2013 16:51:00 +0200 [thread overview]
Message-ID: <20131024145100.GC28149@twin.jikos.cz> (raw)
In-Reply-To: <52672F90.8060804@oracle.com>
On Wed, Oct 23, 2013 at 10:08:16AM +0800, Anand Jain wrote:
> On 10/22/13 10:33 PM, David Sterba wrote:
> >On Tue, Oct 22, 2013 at 01:53:22PM +0800, Anand Jain wrote:
> >>@@ -386,7 +395,7 @@ static int btrfs_scan_kernel(void *search)
> >> static const char * const cmd_show_usage[] = {
> >>- "btrfs filesystem show [options] [<path>|<uuid>]",
> >>+ "btrfs filesystem show [options|<path>|<uuid>]",
> >
> >Options should stay separate from the path/uuid, you're extending the
> >syntax to accept a device:
> >
> > "btrfs filesystem show [options] [<path>|<uuid>|<device>]",
> >
> >I'm fixing it locally, let me know if this doesn't match what you've
> >intended.
>
> I am confused, on how the options should be represented,
> but the internal design is as below.
Hm right, it is a bit confusing, I think because of the syntax that
allows either options or the path/uuid/device specifier, not both, which
is not so common.
I still prefer to keep them separate, because it's something that can be
clarified in the help text or documentation.
Besides, that we may want to add more options that affect
path/uuid/device output, the argument description looks consistent with
other commands and if some combination is not allowed, then an error
message will say why. I really don't expect an average user to think too
hard about it.
david
next prev parent reply other threads:[~2013-10-24 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 5:53 [PATCH 1/2] btrfs-progs: make get_btrfs_mount callable Anand Jain
2013-10-22 5:53 ` [PATCH 2/2] btrfs-progs: filesystem show of specified mounted disk should work Anand Jain
2013-10-22 14:33 ` David Sterba
2013-10-23 2:08 ` Anand Jain
2013-10-24 14:51 ` David Sterba [this message]
2013-10-24 14:54 ` Hugo Mills
2013-10-24 17:21 ` Anand Jain
2013-10-22 16:39 ` David Sterba
2013-10-23 1:53 ` Anand Jain
2013-10-22 14:43 ` [PATCH 1/2] btrfs-progs: make get_btrfs_mount callable David Sterba
2013-10-23 2:11 ` Anand Jain
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=20131024145100.GC28149@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Anand.Jain@oracle.com \
--cc=chris.mason@fusionio.com \
--cc=jbacik@fusionio.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).