From: Xavier Nicollet <nicollet@jeru.org>
To: Michael Niederle <mniederle@gmx.at>
Cc: Goffredo Baroncelli <kreijack@gmail.com>,
linux-btrfs@vger.kernel.org, David Nicol <davidnicol@gmail.com>,
taruishi.hiroak@jp.fujitsu.com
Subject: Re: [RFC] Move all btrfs command to only one command
Date: Fri, 22 Jan 2010 10:33:46 +0100 [thread overview]
Message-ID: <20100122093346.GW29256@jeru.org> (raw)
In-Reply-To: <20100122011107.7bc36b2b@simplux>
Le 22 janvier 2010 =E0 01:11, Michael Niederle a =E9crit:
> > btrfs clone|-c <source> [<dest>/]<name> =20
> > Clone the subvolume <source> with the name <name> i=
n the=20
> > <dest>
> > directory. =
=20
Maybe you should add the "writable snapshot" in the description, since
everyone is using the word "snapshot" on the mailing list.
When I hear "clone", I understand "dump".
> > btrfs delete|-d
> > <subvolume> Delete the subvolume <subvolume>. =
=20
> > btrfs rem|-R <dev> <path>
> > Remove a device to a filesystem
> Just a small suggestion:
> "btrfs remove" instead of "btrfs rem"
Why not "btrfs rm", which reminds "git rm" ?
Actually, I would do something like:
btrfs vol add
btrfs vol rm
btrfs dev add
btrfs dev rm=20
It would bet simpler, wouldn't it ?
--=20
Xavier Nicollet
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-22 9:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 19:29 [RFC] Move all btrfs command to only one command Goffredo Baroncelli
2010-01-22 0:02 ` TARUISI Hiroaki
2010-01-22 0:11 ` Michael Niederle
2010-01-22 9:33 ` Xavier Nicollet [this message]
2010-01-22 8:23 ` Adrian von Bidder
2010-01-24 17:35 ` [RFC] Move all btrfs command to only one command: btrfs.c Goffredo Baroncelli
2010-01-24 18:34 ` Piavlo
2010-02-11 16:33 ` Chris Mason
2010-02-11 18:15 ` Goffredo Baroncelli
2010-02-11 21:20 ` rk
2010-02-11 21:29 ` Goffredo Baroncelli
-- strict thread matches above, loose matches on Subject: below --
2010-08-19 20:52 [RFC] Move all btrfs command to only one command James Smith
2010-08-20 12:03 ` Goffredo Baroncelli
2010-08-20 12:43 ` Jon Nelson
2010-08-20 14:42 ` Benjamin Griese
2010-08-20 18:56 ` Goffredo Baroncelli
2010-08-20 18:27 ` Josh Berry
2010-08-20 18:34 ` Andreas Philipp
2010-08-20 18:49 ` Josh Berry
2010-08-20 19:00 ` Andreas Philipp
2010-08-20 20:28 ` Josh Berry
2010-08-21 4:51 ` James Smith
2010-08-21 9:37 ` Goffredo Baroncelli
[not found] ` <AANLkTikJd8bDU1Eq22u0+yQ8eBCUn3OXHoE5E7uy+SG=@mail.gmail.com>
[not found] ` <AANLkTi=VpZv26jntJ8mwmxtjnQ5LDOn_MSm6VtEhJ1CB@mail.gmail.com>
2010-08-27 3:38 ` James Smith
2010-08-20 19:03 ` Goffredo Baroncelli
2010-08-20 12:12 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=20100122093346.GW29256@jeru.org \
--to=nicollet@jeru.org \
--cc=davidnicol@gmail.com \
--cc=kreijack@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mniederle@gmx.at \
--cc=taruishi.hiroak@jp.fujitsu.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 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).