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

Re: Odd decision of git-pasky-0.7 to do a merge

From
Linus Torvalds <torvalds@osdl.org>
Date
Apr 29, 2005, 17:44 UTC
Message-ID
<Pine.LNX.4.58.0504291043060.18901@ppc970.osdl.org>
In-Reply-To
<20050429083615.A32271@flint.arm.linux.org.uk>
On Fri, 29 Apr 2005, Russell King wrote:
> 
> Why it decided that a merge was necessary is beyond me.  Any ideas?
> Did Linus forget to merge his tree properly?
It looks like it was unable to find the right common ancestor.

If you only had my stuff in it, the common ancestor _should_ have been the parent (c60c390620e0abb60d4ae8c43583714bda27763f), which _should_ have been your old top.

But maybe merge-base didn't work right?
		Linus
Previous: Petr BaudisNext: Russell King
Message 5 of 6 in “Odd decision of git-pasky-0.7 to do a merge”
  1. Russell KingApr 29, 2005
  2. Russell KingApr 29, 2005
  3. Russell KingApr 29, 2005
  4. Petr BaudisApr 29, 2005
  5. Linus TorvaldsApr 29, 2005
  6. Russell KingApr 29, 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.