Re: git-bisect problem

From: Andrew Morton <akpm@osdl.org>
Date: Feb 13, 2006, 09:51 UTC
Message-ID: <20060213015146.26e6c09d.akpm@osdl.org>
In-Reply-To: <20060213093938.GC11053@mythryan2.michonline.com>

Ryan Anderson <ryan@michonline.com> wrote:

Show 23 quoted lines

>
> On Mon, Feb 13, 2006 at 01:32:05AM -0800, Andrew Morton wrote:
> > Junio C Hamano <junkio@cox.net> wrote:
> > >
> > > As humans, we can tell that it is not very plausible that the
> > >  EXTRAVERSION change caused whatever breakage you are chasing,
> > >  but sorry, from your log, I think bisect is doing the right
> > >  thing.
> > 
> > I don't think humans are well-suited to using git.
> > 
> > My current theory is that I was bisecting Linus's tree all along.
> > 
> > What is the correct way in which to switch to git-netdev-all in preparation
> > for performing the bisection?
> 
> First, use "git branch" to show you what branches exist, the * will mark
> the current one.
> 
> Then "git checkout $branch" to switch to one that exists, or "git
> checkout -b $newbranch $sourcebranch" to create a new branch starting
> from $sourcebranch (which can also be a random commit/tag/etc).
>

Yeah, am (ret)trying that.

Assuming I find the bad commit, how do I extract it as a patch?

I tried

git-format-patch -o ~/a 386093ef9a6c88576d8b418bf1c8616d5e410a20 git-netdev-all

and that chewed 10 minutes CPU time and produced no output, so I killed it.