Re: Problem with git bisect in git-1.6.3.3
Hannes,
Thanks for your reply.
2009/7/9 Johannes Sixt <j.sixt@viscovery.net>:
Show 26 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".
>
Ah, it makes sense now. Thanks for your help.
Chris
> -- Hannes
>
>
--
No, Sir; there is nothing which has yet been contrived by man, by which
so much happiness is produced as by a good tavern or inn - Doctor Samuel
Johnson