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

Re: [FILE] Docs update

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Apr 25, 2005, 01:34 UTC
Message-ID
<Pine.LNX.4.21.0504242112190.30848-100000@iabervon.org>
In-Reply-To
<426BF790.9070406@dgreaves.com>

The current merge-base finds the common ancestor with the most recent date. The old algorithm was giving some surprising results, where it didn't always take advantage of a straight line from one side to the other. At some point, I'm going to try to have it find the ancestor with the shortest shorter path, which I think should work best of all.

In any case, I think your documentation should just say it finds as good a common ancestor as possible, since that's what it's really for, regardless of the details of how it decides. Also, it shouldn't be depended on to decide in any particular way.

	-Daniel
*This .sig left intentionally blank*
Previous: David Greaves
Message 5 of 5 in “[FILE] Docs update”
  1. David GreavesApr 24, 2005
  2. Junio C HamanoApr 24, 2005
  3. Linus TorvaldsApr 24, 2005
  4. David GreavesApr 27, 2005
  5. Daniel BarkalowApr 25, 2005

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.