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

Re: [PATCH/resend] Documentation: update to git-merge-base --octopus

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 15, 2011, 17:18 UTC
Message-ID
<7v39lje8mp.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4DA80549.5040600@lyx.org>
Vincent van Ravesteijn <vfr@lyx.org> writes:
Show 10 quoted lines
>>> +When the option `--octopus` is given, the result of `git merge-base A B C`
>>> > +will be '2', because '2' is the common ancestor of all branches.
>> 
>> Wouldn't it be easier to read if you had the option in the command line, i.e.
>> 
>>     The result of `git merge-base --octopus A B C` is '2' because...
>> 
>> without "When ... given" that now become noisewords?
>
> Yes, that's much better. I included it in the rerolled patch series.
Makes sense.  Will queue both patches.
Thanks, both.
Previous: Vincent van RavesteijnNext: Vincent van Ravesteijn
Message 5 of 7 in “Documentation: update to git-merge-base --octopus”
  1. Documentation: update to git-merge-base --octopusVincent van Ravesteijn, Apr 12, 2011
  2. Junio C HamanoApr 12, 2011
  3. Jonathan NiederApr 12, 2011
  4. Vincent van RavesteijnApr 15, 2011
  5. Junio C HamanoApr 15, 2011
  6. 1/2 Documentation: update to git-merge-base --octopusVincent van Ravesteijn, Apr 15, 2011
  7. 2/2 Restructure documentation for git-merge-base.Vincent van Ravesteijn, Apr 15, 2011

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.