https://bugs.freedesktop.org/show_bug.cgi?id=111244
--- Comment #5 from Michel Dänzer <mic...@daenzer.net> ---
(In reply to cspack from comment #4)
> The first bisect pointed to a merge commit so the second was done to bisect
> within the merged commits.
That doesn't invalidate my previous comment. :) git bisect identifying a merge
commit already indicates the same thing by itself. In particular, the fact that
it identified a merge commit means that you declared all of its parent commits
good.
(There *are* rare cases where a problem is actually introduced by a merge
commit itself, but then the second bisection should have either identified the
same merge commit again (if you tested it again), or failed, because all the
other commits you tested should have been good again.)
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
