On Tue, 2011-05-31 at 20:02 -0700, Christian Kujau wrote: > (Cc'in Linus) > > On Tue, 31 May 2011 at 17:48, Christian Kujau wrote: > > In the meantime, "git bisect" behaves kinda weird, I don't know what went > > wrong here: > > > > $ git bisect start > > $ git bisect good # Linux 2.6.39 > > $ git bisect bad v3.0-rc1 # Linux 3.0-rc1 > > $ git bisect bad # c44dead70a... > > $ git bisect bad # d93515611b.. > > > > ...yet the ./Makefile shows[0] that I'm already way behind: 2.6.39-rc2. > > Maybe "git bisect" got confused with that whole 2.6.x -> 3.0 renaming? > > Hm, I tried again, from a clean v3.0-rc1 (git reset --hard), but after the > 2nd "git bad" I'm at 2.6.39-rc2 again - while I /should/ be somwhere > inbetween v2.6.39..v3.0-rc1, right?
Kernel version is totally irrelevant when bisecting. You are not walking through a linear series of patches but a complex tree of merges which might have forked off different versions in the first place. Cheers, Ben. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev