* [WARNING] please stop using git.git "next" for now
@ 2006-05-03 21:53 Junio C Hamano
2006-05-03 23:13 ` Junio C Hamano
0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2006-05-03 21:53 UTC (permalink / raw)
To: git; +Cc: linux-kernel
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [WARNING] please stop using git.git "next" for now
2006-05-03 21:53 [WARNING] please stop using git.git "next" for now Junio C Hamano
@ 2006-05-03 23:13 ` Junio C Hamano
2006-05-04 0:46 ` Junio C Hamano
0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2006-05-03 23:13 UTC (permalink / raw)
To: git; +Cc: linux-kernel
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [WARNING] please stop using git.git "next" for now
2006-05-03 23:13 ` Junio C Hamano
@ 2006-05-04 0:46 ` Junio C Hamano
0 siblings, 0 replies; 3+ messages in thread
From: Junio C Hamano @ 2006-05-04 0:46 UTC (permalink / raw)
To: git
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-05-04 0:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-03 21:53 [WARNING] please stop using git.git "next" for now Junio C Hamano
2006-05-03 23:13 ` Junio C Hamano
2006-05-04 0:46 ` Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).