Re: Problem with git bisect in git-1.6.3.3

From: Christian Couder <chriscool@tuxfamily.org>
Date: Jul 10, 2009, 05:05 UTC
Message-ID: <200907100705.24199.chriscool@tuxfamily.org>
In-Reply-To: <4A5590A3.8070404@viscovery.net>

On Thursday 09 July 2009, Johannes Sixt wrote:

Show 29 quoted lines

> Chris Clayton schrieb:
> > git bisect start
> > # good: [07a2039b8eb0af4ff464efd3dfd95de5c02648c6] Linux 2.6.30
> > git bisect good 07a2039b8eb0af4ff464efd3dfd95de5c02648c6
> > # bad: [8e4a718ff38d8539938ec3421935904c27e00c39] Linux 2.6.31-rc2
>
> ...
>
> > but, from Makefile, it appears the last "bad" has placed me at a
> > change earlier than 2.6.30:
> >
> > [chris:~/kernel/linux-2.6]$ head Makefile
> > VERSION = 2
> > PATCHLEVEL = 6
> > SUBLEVEL = 30
> > EXTRAVERSION = -rc6
>
> ...
>
> > I'm not an experienced git user, so it may be that I have made an
> > error or false assumption.
>
> Not an error, but false assumptions:
>
> http://thread.gmane.org/gmane.comp.version-control.git/99967/focus=99977
>
> Just continue bisecting. If you can't test the version that bisect warps
> you to because the feature where the bug happens is not present, mark
> that revision as "good".

For information, I added the following very short FAQ entry:

http://git.or.cz/gitwiki/GitFaq#Whydoes.22gitbisect.22makesmetestversionsoutsidethe.22good-bad.22range.3F

Thanks, Christian.