On 25/10/19 7:51 AM, Anand Jain wrote:
On 24/10/19 11:41 PM, David Sterba wrote:
On Thu, Oct 24, 2019 at 02:28:22PM +0800, Anand Jain wrote:
When both the options (--quiet and --verbose) in btrfs send and receive
is specified, we need at least one of it to overrule the other,
irrespective
of the chronological order of options.
I think the common behaviour is to respect the order of appearance on
the commandline.
I am fine with this. Will fix it as this.
Question: command -v -q -v should be equal to command -v, right?
Thanks, Anand
(IMO generally command -q is used in scripts so it makes sense to keep
it absolutely quiet when used. Where as -v is used for
understanding.).
So 'command -vvv -q' will be the same as 'command -q',
while 'command -q -vvv' will be 'command -vvv'.
We need to fix this. As of now command -q -vvv is command -vv.
Thanks, Anand
Eg. ssh behaves like that, OTOH rsync does not and -q beats -vvv. I
don't know about other commands that accept multiple -v and -q to get
more samples. The usage pattern where order on command line matters is
following the idea where there's a long line and adding -vvv to the end
will make it verbose.
