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

Re: [PATCH] Update the documentation for git-merge-base

From
Junio C Hamano <junkio@cox.net>
Date
May 16, 2006, 06:13 UTC
Message-ID
<7vhd3qebuv.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060516055815.GA4572@c165.ib.student.liu.se>
Fredrik Kuivinen <freku045@student.liu.se> writes:
> Is the code guaranteed to return a least common ancestor? If that is
> the case we should probably mention it in the documentation.

Unfortunately, no, if you mean by "least common" closest to the tips.

See the big illustration at the top of the source for how you can construct pathological case to defeat an attempt to guarantee such. --all guarantees that the output contains all interesting ones, but does not guarantee the output has no suboptimal merge bases.

Previous: Fredrik KuivinenNext: Fredrik Kuivinen
Message 2 of 7 in “Update the documentation for git-merge-base”
  1. Update the documentation for git-merge-baseFredrik Kuivinen, May 16, 2006
  2. Junio C HamanoMay 16, 2006
  3. Fredrik KuivinenMay 16, 2006
  4. Junio C HamanoMay 16, 2006
  5. Linus TorvaldsMay 16, 2006
  6. Linus TorvaldsMay 16, 2006
  7. Junio C HamanoMay 16, 2006

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.