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

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

From
PBPaul Bolle <pebolle@tiscali.nl>
Date
Aug 12, 2009, 20:47 UTC
Message-ID
<1250110060.2500.8.camel@x61.thuisdomein>
In-Reply-To
<7vhbwcydtn.fsf@alter.siamese.dyndns.org>
On Wed, 2009-08-12 at 13:31 -0700, Junio C Hamano wrote:
> Paul Bolle <pebolle@tiscali.nl> writes:
> 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?

I guess not (these two were the ones that annoyed me enough to write patches when I read them in order to learn more about the commands they described).

What is the best way to fix small issues like this: one set of patches that tries to fix as much as possible in one go or a stream of little patches whenever similar issues are found in one of the documents?

Previous: Junio C Hamano
Message 9 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.