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

Re: git-merge-recursive segmentation error

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 20, 2006, 02:33 UTC
Message-ID
<Pine.LNX.4.63.0612200332420.19693@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7vpsafmh89.fsf@assigned-by-dhcp.cox.net>
Hi,
On Tue, 19 Dec 2006, Junio C Hamano wrote:
Show 13 quoted lines
> Junio C Hamano <junkio@cox.net> writes:
> 
> > Luben Tuikov <ltuikov@yahoo.com> writes:
> >
> >> 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.
> 
> 1510fe is buggy and it is my fault.

You hand munging should not have led to any segmentation fault. It would be sooo nice to have the test case.

Ciao,
Previous: Junio C HamanoNext: Luben Tuikov
Message 3 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.