All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: <dsterba@suse.cz>, Omar Sandoval <osandov@fb.com>,
	<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/2] btrfs device remove alias
Date: Thu, 25 Jun 2015 09:45:45 -0400	[thread overview]
Message-ID: <20150625134545.GC3920@ret.masoncoding.com> (raw)
In-Reply-To: <20150625134151.GH726@twin.jikos.cz>

On Thu, Jun 25, 2015 at 03:41:51PM +0200, David Sterba wrote:
> On Wed, Jun 24, 2015 at 09:09:15AM -0700, Omar Sandoval wrote:
> > The opposite of btrfs device add is btrfs device delete. This really
> > should be btrfs device remove.
> 
> I think people got used to the 'delete' command over time, but for
> convenience I don't mind to add the alias. Also you delete files by 'rm'
> which is short for 'remove' and probably don't mind either.

I do agree that people got used to delete, but its one of those things
that new users are likely to trip over.  And since we're highly unlikely
to ever use 'rm' for something other than deletion, it makes sense to
just alias them.

-chris

  reply	other threads:[~2015-06-25 13:45 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 [this message]
2015-06-26  1:10 ` Anand Jain
2015-06-26  4:21   ` Duncan
2015-06-26 13:33   ` David Sterba
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=20150625134545.GC3920@ret.masoncoding.com \
    --to=clm@fb.com \
    --cc=dsterba@suse.cz \
    --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.