https://bugzilla.kernel.org/show_bug.cgi?id=193981
--- Comment #14 from Michel Dänzer (mic...@daenzer.net) --- First of all, you can just run "git bisect skip" for any commits where you can't test for the problem you're bisecting, for any reason. With luck, this will allow git bisect to identify the regressing commit anyway. Even if not, it'll provide a range of candidate commits, which can be further narrowed down using Felix's technique. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
