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

Re: SIGSEGV in merge recursive

From
Junio C Hamano <junkio@cox.net>
Date
Dec 31, 2006, 02:30 UTC
Message-ID
<7vvejshk4c.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<10871.51671.qm@web31801.mail.mud.yahoo.com>
Luben Tuikov <ltuikov@yahoo.com> writes:
> So it appears that the fix is in "master", but not in "next".
>
> Junio, can you confirm this?

It was merged into 'next' with 1e48a691, about 2 hours after I merged the fix 5d6b151f to 'master'. Sometimes when I have a fix that is urgent enough, I push out only 'master' before merging and retesting it in 'next', so it is plausible that your fetch grabbed such a state.

Previous: Luben TuikovNext: Luben Tuikov
Message 7 of 8 in “SIGSEGV in merge recursive”
  1. Luben TuikovDec 29, 2006
  2. Junio C HamanoDec 29, 2006
  3. Luben TuikovDec 29, 2006
  4. Johannes SchindelinDec 30, 2006
  5. Florian WeimerDec 30, 2006
  6. Luben TuikovDec 31, 2006
  7. Junio C HamanoDec 31, 2006
  8. Luben TuikovDec 31, 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.