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

3 messages from 2006-05-03 to 2006-05-04. Participants: Junio C Hamano.
Thread: https://gitlist.dev/t/4045

## Junio C Hamano, 2006-05-03 21:53

Subject: [WARNING] please stop using git.git "next" for now
Message-ID: <7virombwro.fsf@assigned-by-dhcp.cox.net>
URL: https://gitlist.dev/e/7virombwro.fsf%40assigned-by-dhcp.cox.net

```
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.

```

## Junio C Hamano, 2006-05-03 23:13

Subject: Re: [WARNING] please stop using git.git "next" for now
Message-ID: <7vejzabt2b.fsf@assigned-by-dhcp.cox.net>
URL: https://gitlist.dev/e/7vejzabt2b.fsf%40assigned-by-dhcp.cox.net
In-Reply-To: <7virombwro.fsf@assigned-by-dhcp.cox.net>

```
Junio C Hamano <junkio@cox.net> writes:

> 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.

```

## Junio C Hamano, 2006-05-04 00:46

Subject: Re: [WARNING] please stop using git.git "next" for now
Message-ID: <7vwtd2aa6l.fsf@assigned-by-dhcp.cox.net>
URL: https://gitlist.dev/e/7vwtd2aa6l.fsf%40assigned-by-dhcp.cox.net
In-Reply-To: <7vejzabt2b.fsf@assigned-by-dhcp.cox.net>

```
Junio C Hamano <junkio@cox.net> writes:

>> 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.

```
