Hi Andres,
Andres Cimmarusti wrote:
>> To be clear, are you saying "git bisect" told you that 76531d4166 was
>> the first bad commit?
>
> Not exactly. I told you I got confused on how to use git-bisect
My bad. I forgot I hadn't given the git bisect demo.
So, it works like this:
git bisect start; # we're bisecting!
git bisect bad v3.2.4
git bisect bad 76531d4166; # tested bad
... continue listing bad commits ...
git bisect good 7d339ae99
Now git will choose a version to test. So:
make silentoldconfig; # reuse configuration
make -j4 deb-pkg
That produces a package to try. Once you see how it behaves, you can do:
git bisect good; # if it shows one HDMI output
git bisect bad; # if it shows three
git bisect skip; # if some other bug makes it hard to test
And then git will check out another commit for you.
If you have the gitk package installed, you can run "git bisect visualize"
at any step to watch the regression range narrowing. Eventually it will
find the first bad commit, but if you're bored before then, you can run
"git bisect log" to get a log others can use to pick up where you left off.
Thanks and hope that helps,
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
