On Mon, Aug 24, 2015 at 8:44 PM, Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: > Karthik Nayak <karthik.188@xxxxxxxxx> writes: > >> On Mon, Aug 24, 2015 at 1:26 AM, Matthieu Moy >> <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: >>> Karthik Nayak <karthik.188@xxxxxxxxx> writes: >>> >>>> --- a/Documentation/git-tag.txt >>>> +++ b/Documentation/git-tag.txt >>>> @@ -13,7 +13,8 @@ SYNOPSIS >>>> <tagname> [<commit> | <object>] >>>> 'git tag' -d <tagname>... >>>> 'git tag' [-n[<num>]] -l [--contains <commit>] [--points-at <object>] >>>> - [--column[=<options>] | --no-column] [--create-reflog] [--sort=<key>] [<pattern>...] >>>> + [--column[=<options>] | --no-column] [--create-reflog] [--sort=<key>] >>>> + [--format=<format>] [<pattern>...] >>>> 'git tag' -v <tagname>... >>>> >>>> DESCRIPTION >>>> @@ -158,6 +159,11 @@ This option is only applicable when listing tags without annotation lines. >>>> The object that the new tag will refer to, usually a commit. >>>> Defaults to HEAD. >>>> >>>> +<format>:: >>> >>> Shouldn't this be --format <format>, not just <format>? We usually use >>> the named argument in the SYNOPSIS for positional arguments, but not for >>> arguments following an option. >> >> This is how it was in for-each-ref Documentation, hence to keep it similar I >> just put <format>. > > "It's wrong in another place" sounds like an argument to fix the other > place, not to get it wrong here too ;-). > Of course! That was just me justifying my action. I agree, it should be corrected both places. -- Regards, Karthik Nayak -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html