News for hackers. Stuff that matters.
Re:Finding a kernel regression in half an hour with git bise... by kazinator on Thursday July 29, 2021 @02:17PM (#27999655)
Well, find the commit where the behavior is introduced, in any case.

Or, in some cases, multiple possible commits. If the bad commit is preceded or followed by untestable commits (declared that way via "git bisect skip", they are implicated also).

There are no comments on this comment yet.