Re: git-bisect problem

From: Ryan Anderson <ryan@michonline.com>
Date: Feb 13, 2006, 09:39 UTC
Message-ID: <20060213093938.GC11053@mythryan2.michonline.com>
In-Reply-To: <20060213013205.4ba47836.akpm@osdl.org>

On Mon, Feb 13, 2006 at 01:32:05AM -0800, Andrew Morton wrote:

Show 13 quoted lines

> 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).

-- 
Ryan Anderson
  sometimes Pug Majere