On Thursday 18 February 2010, Chris Mason wrote: > I do like the subcommand method, more details below. > > On Wed, Feb 17, 2010 at 03:35:26PM -0800, Mike Fedyk wrote: > > I think he need some command hierarchy here. > > > > On Wed, Feb 17, 2010 at 12:02 PM, Goffredo Baroncelli > > <kreij...@gmail.com> wrote: > > > OPTIONS > > > snapshot|-s <source> [<dest>/]<name> > > > Create a writeble snapshot of the subvolume <source> with the > > > name <name> in the <dest> directory. If <source> is not a sub‐ > > > volume, btrfs returns an error. > > > > This should be "btrfs subvolume snapshot <source> [<dest>/]<name>". > > It only works on subvolumes. > > If we can type subvol instead of subvolume I like it. Basically the > perl/python arg parsing system where any short form of the command that > uniquely matches it is allowed.
So for you $ btrfs s s <source> <dest> is OK ? ('btrfs s s' means btrfs subvolume snapshot) > We keep the long forms but allow the user to pick a shorter form if it > isn't ambiguous. -- gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreij...@inwind.it> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html