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

Re: [PATCH] Re: [TRIVIAL] Documentation: merge: one <remote> is required

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 12, 2009, 20:31 UTC
Message-ID
<7vhbwcydtn.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1250074578.7545.2.camel@localhost.localdomain>
Paul Bolle <pebolle@tiscali.nl> writes:
Show 11 quoted lines
> Confusingly, as far as I can see, the manpages of the following commands
> seem to use the "one or more" meaning:
>     git merge-base
> ...
> ("git mv" uses both meanings in its synopsis. The two "git tag"
> invocations seem to do nothing with zero arguments and do not return an
> error.)
>
> If the above commands really use the "one or more" meaning, that would
> mean both versions are used in the documentation. I'd say it would be
> better to stick to one meaning throughout the manpages.
You are absolutely right.  We would want consistency.

I do not have any objection to make sure that we uniformly use ellipses for one-or-more (and enclose them in [] if we want zero-or-more). Are these two that your patch touched the only ones that need fixing?

Previous: Paul BolleNext: Paul Bolle
Message 8 of 9 in “[TRIVIAL] Documentation: merge: one <remote> is required”
  1. [TRIVIAL] Documentation: merge: one <remote> is requiredPaul Bolle, Aug 11, 2009
  2. Re: [TRIVIAL] Documentation: merge: one <remote> is requiredNicolas Sebrecht, Aug 11, 2009
  3. Paul BolleAug 11, 2009
  4. Junio C HamanoAug 12, 2009
  5. Jakub NarebskiAug 12, 2009
  6. Re: [TRIVIAL] Documentation: merge: one <remote> is requiredNicolas Sebrecht, Aug 12, 2009
  7. Paul BolleAug 12, 2009
  8. Junio C HamanoAug 12, 2009
  9. Paul BolleAug 12, 2009

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.