From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S1751371AbWECVxf@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751371AbWECVxf (ORCPT <rfc822;willy@w.ods.org>);
	Wed, 3 May 2006 17:53:35 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751370AbWECVxe
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 3 May 2006 17:53:34 -0400
Received: from fed1rmmtao05.cox.net ([68.230.241.34]:21720 "EHLO
	fed1rmmtao05.cox.net") by vger.kernel.org with ESMTP
	id S1751368AbWECVxd (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 3 May 2006 17:53:33 -0400
From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: [WARNING] please stop using git.git "next" for now
cc: linux-kernel@vger.kernel.org
Date: Wed, 03 May 2006 14:53:31 -0700
Message-ID: <7virombwro.fsf@assigned-by-dhcp.cox.net>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

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.