From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs device remove alias
Date: Fri, 26 Jun 2015 04:21:43 +0000 (UTC) [thread overview]
Message-ID: <pan$8773$4ae88d92$9e16c06b$550d1efe@cox.net> (raw)
In-Reply-To: 558CA6A0.20401@oracle.com
Anand Jain posted on Fri, 26 Jun 2015 09:10:56 +0800 as excerpted:
> while on this. its also good idea to create alias for
>
> btrfs replace start -> btrfs device replace.
>
> any comments ?
That's actually the one that makes more sense to me. Delete/remove/
subtract, all about the same to me, so while I'm not opposed to alias for
that, I don't really see the need. But with btrfs device add/remove,
having btrfs replace instead of btrfs device replace, makes absolutely no
sense to me, so I'm all for that alias.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-06-26 4:21 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 [this message]
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='pan$8773$4ae88d92$9e16c06b$550d1efe@cox.net' \
--to=1i5t5.duncan@cox.net \
--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