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 3, 2006, 23:13 UTC
Message-ID
<7vejzabt2b.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<7virombwro.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 11 quoted lines
> I just noticed there is a breakage in write-tree optimization
> that uses the new cache-tree data structure in the "next"
> branch.  Switching branches with "git checkout anotherbranch"
> when your index exactly matches the current HEAD commit and then
> immediately doing write-tree produces a nonsense tree, and
> commits on top of that results in tree objects that have
> duplicated entries.
>
> 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.

Sorry for the noise.
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 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.