Re: [PATCH v17 14/14] tag.c: implement '--merged' and '--no-merged' options
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Sep 18, 2015, 07:10 UTC
- Message-ID
- <vpqoah0kxtb.fsf@anie.imag.fr>
- In-Reply-To
- <xmqq37ycitps.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 20 quoted lines
> John Keeping <john@keeping.me.uk> writes: > >>> +--[no-]merged [<commit>]:: >> >> We prefer to write --[no-]* as: >> >> --option:: >> --no-option:: >> >> although this may be the first instance that we see this combination >> with an argument. >> >> I also found the "[<commit>]" syntax confusing and had to go and figure >> out what PARSE_OPT_LASTARG_DEFAULT does; I wonder if it's worth >> appending something like the following to the help for this option: >> >> The `commit` may be omitted if this is the final argument. > > "may be omitted" must be followed by a description of what happens > when omitted (i.e. "defaults to ...").
Then:
The `commit` may be omitted and defaults to HEAD if this is the final argument.
Sounds good to me.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/