git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	torvalds@linux-foundation.org
Subject: Re: current git kernel has strange problems during bisect
Date: Sun, 11 Jan 2009 16:20:03 +0100	[thread overview]
Message-ID: <200901111620.03345.borntraeger@de.ibm.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0901111613250.3586@pacific.mpi-cbg.de>


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

  reply	other threads:[~2009-01-11 15:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 15:02 current git kernel has strange problems during bisect Christian Borntraeger
2009-01-11 15:07 ` Christian Borntraeger
2009-01-11 15:14   ` Johannes Schindelin
2009-01-11 15:20     ` Christian Borntraeger [this message]
2009-01-11 16:31       ` Boaz Harrosh
2009-01-11 19:13       ` Linus Torvalds
2009-01-11 19:42         ` Sam Ravnborg
2009-01-11 19:47           ` Alexey Zaytsev
2009-01-11 23:02             ` Pierre Habouzit
2009-01-12  4:51               ` Christian Couder
2009-01-12  5:03                 ` Christian Couder
2009-01-11 20:04           ` Linus Torvalds
2009-01-11 21:39             ` Christian Borntraeger
2009-01-11 22:27               ` Daniel Barkalow
2009-01-13 20:26               ` Kyle Moffett
2009-01-15 16:54                 ` Andreas Bombe
2009-01-15 23:13                   ` Kyle Moffett
2009-01-11 21:54             ` Sam Ravnborg
2009-01-11 22:17             ` Alexey Zaytsev
2009-01-11 22:32               ` Sam Ravnborg
2009-01-11 22:34               ` Daniel Barkalow
2009-01-11 20:29         ` Andi Kleen
2009-01-11 20:51           ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200901111620.03345.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).