https://bugzilla.kernel.org/show_bug.cgi?id=85421
--- Comment #25 from Michel Dänzer <michel at daenzer.net> --- (In reply to Hin-Tak Leung from comment #24) > [...] which is still a big bunch to look at what made 10.3.x > unstable. That's what git bisect is for. It can isolate a change with the minimum number of tests required (approximately log2 of the number of commits between the known good and bad). > It would be easier if the crashes are more "reproducible". Indeed, so if you do try to bisect it, it's important that you test each commit long enough to be sure it's 'more stable' before declaring it as good. -- You are receiving this mail because: You are watching the assignee of the bug.
