On Tue, Jun 10, 2014 at 9:02 AM, <Valdis.Kletnieks@xxxxxx> wrote:
> On Tue, 10 Jun 2014 08:26:12 -0500, Greg Donald said:
>
>> the end. All 7 of the bisected kernels I built yesterday boot just
>> fine.
>
> Just to clarify - did 'git bisect' report a 'first bad commit is NNNN'?
My last "git bisect good" reported this:
1860e379875dfe7271c649058aeddffe5afd9d0d is the first bad commit
commit 1860e379875dfe7271c649058aeddffe5afd9d0d
Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date: Sun Jun 8 11:19:54 2014 -0700
Linux 3.15
:100644 100644 cdaa5b6a1c4d6e43e4c0c784831e1e3cb0d9fae5
6d1e304943a379c126c40e2aa1eb3bf4e872ecb1 M Makefile
But that doesn't appear to be a bad commit, it's just the version bump
from v3.15-rc8 to v3.15. I can only guess it's (wrongly) saying
that's a bad commit because there's nothing left to bisect.
> Just wondering if the bisect in fact finished, or if you had an 8th bisect
> still to do....
It appears I have completed the full bisection at 7 bisections.
Running "git bisect good" again reports the same commit above.
I was following this guide:
https://www.kernel.org/pub/software/scm/git/docs/git-bisect-lk2009.html
Thanks,
--
Greg Donald
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
