Re: git status -u is mildly astonishing
- From
Jeff King <peff@peff.net>
- Date
- Sep 17, 2015, 17:43 UTC
- Message-ID
- <20150917174306.GA29171@sigill.intra.peff.net>
- In-Reply-To
- <vpqd1xhqfxg.fsf@anie.imag.fr>
On Thu, Sep 17, 2015 at 04:27:39PM +0200, Matthieu Moy wrote:
Show 9 quoted lines
> > Therefore I would argue that -u is behaving differently from other
> > arguments (especially when considered across all git subcommands)
>
> This is because you have options with non-optional argument in mind, or
> options that have no short version.
>
> If I grep the source correctly, the only options accepting a short
> version and an optional string argument are "{merge,am,commit,revert}
> -S", "grep -O" and "status -u", which behave consistantly.Exactly. This is covered in gitcli(7)*, but I wonder if it is worth calling attention to this behavior specifically in the documentation of those options.
-Peff
[*] Try "git help cli", the bit starting with 'Here are the rules
regarding the "flags"...'.