git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] doc/for-each-ref: explicitly specify option names

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 2, 2017, 02:03 UTC
Message-ID
<xmqqk21hj1qw.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170901144931.26114-1-me@ikke.info>
Kevin Daudt <me@ikke.info> writes:
Show 9 quoted lines
> For count, sort and format, only the argument names were listed under
> OPTIONS, not the option names.
>
> Add the option names to make it clear the options exist
>
> Signed-off-by: Kevin Daudt <me@ikke.info>
> ---
>  Documentation/git-for-each-ref.txt | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)

Sounds sensible. First I thought this was done deliberately because these placeholder can apply to more than one option and we wanted to explain each thing only once (e.g. "<object>" appears in 5 places, and having to repeat something like "you can spell <object> by the unique prefix of the object name, or the name of a ref that points at it, or ..." in each option would be awkward), but that is not the case here.

While we are at it, I just noticed that the SYNOPSIS section makes it look as if <pattern>... must come before points-at, merged, and their friends, but I do not think that should be the case. I also notice that unlike --sort/--format/... the last four/five options are spelled with "--option <value>" syntax; we should consistently use "--option=<value>" instead there.

But these two are separate issues that can be fixed in a patch separate from this one I am responding to.

p.s. I am still mostly offline and won't be doing any reviews or queuing that requires me to look at anything beyond the patch context. Please do not get disappointed if you do not see your patch in my tree until later next week.

Previous: Jonathan NiederNext: Kevin Daudt
Message 5 of 9 in “doc/for-each-ref: explicitly specify option names”
  1. doc/for-each-ref: explicitly specify option namesKevin Daudt, Sep 1, 2017
  2. Jeff KingSep 1, 2017
  3. Johannes SchindelinSep 1, 2017
  4. Jonathan NiederSep 1, 2017
  5. Junio C HamanoSep 2, 2017
  6. 1/2 doc/for-each-ref: consistently use '=' to between argument names and valuesKevin Daudt, Sep 11, 2017
  7. 2/2 doc/for-each-ref: explicitly specify option namesKevin Daudt, Sep 11, 2017
  8. Junio C HamanoSep 12, 2017
  9. Kevin DaudtSep 12, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.