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

Re: [WARNING] please stop using git.git "next" for now

From
Junio C Hamano <junkio@cox.net>
Date
May 4, 2006, 00:46 UTC
Message-ID
<7vwtd2aa6l.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<7vejzabt2b.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 7 quoted lines
>> I will be working on a fix now, but in the meantime please do
>> not use the "next" branch for real work.  Sorry for the
>> breakage.
>
> Two-way merge by read-tree forgot to invalidate the directories
> a new element was added underneath.  The fix is simple and will
> be in the "next" I'll push out tonight.

OK, done. Will be looking into "binary grep segfault" problem next.

Previous: Junio C Hamano
Message 3 of 3 in “[WARNING] please stop using git.git "next" for now”
  1. Junio C HamanoMay 3, 2006
  2. Junio C HamanoMay 3, 2006
  3. Junio C HamanoMay 4, 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.