Comment # 16
on bug 92858
from Darren D.
(In reply to Michel Dänzer from comment #15) > (In reply to Michel Dänzer from comment #14) > > ... I think you'll need to restart the bisection process with > > 744b058827b3db9a4f6027522dd9c73a208c2d31 as the initial good commit [...] > > Actually, you can start with 91d9f9856f91c82ac6289a0fff65dd12cfa07e34 as the > initial good commit. I can restart it yet again, and at least this time it'll be a narrower range of commits. And this is the sequence of commands I should use to do that, correct? git bisect start git bisect good 91d9f9856f91c82ac6289a0fff65dd12cfa07e34 git bisect bad 692a59e696afe1a4e777d0e4359325336ab0ad89 And if I start running into unbootable kernels again, I should start a new bisect with a different copy of the source tree and identify at which commit the compiled kernel started failing to boot, shouldn't I?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
