From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: Omar Sandoval <osandov@fb.com>,
linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.cz>,
Chris Mason <clm@fb.com>
Subject: Re: [PATCH 0/2] btrfs device remove alias
Date: Fri, 26 Jun 2015 15:33:23 +0200 [thread overview]
Message-ID: <20150626133323.GS726@twin.jikos.cz> (raw)
In-Reply-To: <558CA6A0.20401@oracle.com>
On Fri, Jun 26, 2015 at 09:10:56AM +0800, Anand Jain wrote:
> while on this. its also good idea to create alias for
>
> btrfs replace start -> btrfs device replace.
This was asked for back then, and briefly discussed on irc (11/2012).
The preference was not to do too much typing, although the command
hierarchy would become less structured and can cause some trouble when
looking for docs.
I'm slightly worried about adding more aliases as it can cause confusion
when writing documentaiton and recommending how to do things. But I
understand the motivations to make the interface more consistent or
convenient to use.
In this case it's moving replace to the expected place. I'm not against
it but more feedback would help.
next prev parent reply other threads:[~2015-06-26 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 16:09 [PATCH 0/2] btrfs device remove alias Omar Sandoval
2015-06-24 16:09 ` [PATCH 1/2] btrfs-progs: replace struct cmd_group->hidden with flags Omar Sandoval
2015-06-26 14:34 ` David Sterba
2015-06-24 16:09 ` [PATCH 2/2] btrfs-progs: alias btrfs device delete to btrfs device remove Omar Sandoval
2015-06-26 14:46 ` David Sterba
2015-06-25 4:06 ` [PATCH 0/2] btrfs device remove alias Duncan
2015-06-25 13:41 ` David Sterba
2015-06-25 13:45 ` Chris Mason
2015-06-26 1:10 ` Anand Jain
2015-06-26 4:21 ` Duncan
2015-06-26 13:33 ` David Sterba [this message]
2015-06-27 11:38 ` 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=20150626133323.GS726@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@fb.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 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.