Re: [PATCH] btrfs: use full subcommand name at _btrfs_get_subvolid()

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]



On Fri, Sep 22, 2023 at 05:18:35PM +0200, David Disseldorp wrote:
> On Fri, 22 Sep 2023 12:45:01 +0100, fdmanana@xxxxxxxxxx wrote:
> 
> > From: Filipe Manana <fdmanana@xxxxxxxx>
> > 
> > Avoid using the shortcut "sub" for the "subvolume" command, as this is the
> > standard practice because such shortcuts are not guaranteed to exist in
> > every btrfs-progs release (they may come and go). Also make the variables
> > local.
> 
> Hmm, having them come and go would likely break quite a few user
> scripts...

The help text of 'btrfs' says at the end:

"For an overview of a given command use 'btrfs command --help'
 or 'btrfs [command...] --help --full' to print all available options.
 Any command name can be shortened as far as it stays unambiguous,
 however it is recommended to use full command names in scripts.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

 All command groups have their manual page named 'btrfs-<group>'."


The commands will not disappear but new commands may be added and the
prefix would become ambiguous. The short versions are accepted for
manual command typing convenience, scripts should use the full length.



[Index of Archives]     [Linux Filesystems Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux