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

Re: git-merge-recursive segmentation error

From
Junio C Hamano <junkio@cox.net>
Date
Dec 20, 2006, 02:25 UTC
Message-ID
<7vtzzrmhhd.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<929899.78332.qm@web31809.mail.mud.yahoo.com>
Luben Tuikov <ltuikov@yahoo.com> writes:
Show 5 quoted lines
> I also ran git-bisect twice over two well known but overlapping
> good-bad regions and I get the same commit as being the culprit.
> It seems to be commit 1510fea781cb0517eeba8c378964f7bc4f9577ab.
>
>     Luben
Ooooooops.
Next: Junio C Hamano
Message 1 of 6 in “Re: git-merge-recursive segmentation error”
  1. Junio C HamanoDec 20, 2006
  2. Junio C HamanoDec 20, 2006
  3. Johannes SchindelinDec 20, 2006
  4. Luben TuikovDec 20, 2006
  5. Shawn PearceDec 20, 2006
  6. Junio C HamanoDec 20, 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.