From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: current git kernel has strange problems during bisect
Date: Sun, 11 Jan 2009 16:20:03 +0100
User-Agent: KMail/1.9.9
Cc: git@vger.kernel.org,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       torvalds@linux-foundation.org
References: <200901111602.53082.borntraeger@de.ibm.com> <200901111607.59054.borntraeger@de.ibm.com> <alpine.DEB.1.00.0901111613250.3586@pacific.mpi-cbg.de>
In-Reply-To: <alpine.DEB.1.00.0901111613250.3586@pacific.mpi-cbg.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200901111620.03345.borntraeger@de.ibm.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1107
Lines: 36


Am Sonntag 11 Januar 2009 schrieben Sie:
> Hi,
> 
> On Sun, 11 Jan 2009, Christian Borntraeger wrote:
> 
> > Am Sonntag 11 Januar 2009 schrieb Christian Borntraeger:
> > > doing a 
> > > git bisect start
> > > git bisect good a3a798c
> > > git bisect bad v2.6.29-rc1
> > > 
> > > results in a repository without several files, e.g Makefile!
> > > git describe also fails.
> > 
> > In fact, retesting with a clean repository shows, that there are only 
btrfs 
> > files - nothing else.
> > 
> > Linus did you pull a broken btrfs repository?
> 
> I guess it is a subtree merge.  So no, nothing went wrong
> 
> Use "git bisect skip" to skip over those.

I think we should really avoid merging subtrees to the linux kernel. It makes 
bisecting a real PITA. 
Furthermore, It is unlikely, but what if the problem is part of the 581 
changesets from btrfs?

Christian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/