git bisect should return 1 when the first bad commit is found

From: Pedro Larroy <hidden>
Date: 2019-06-13 17:11:01

Hi

I'm using git bisect, and for complex reasons I can't use git bisect
run to drive the bisection. I don't think git bisect bad/good is
returning a different status code when the first bad commit is found
and this would be very useful to stop the driver of the bisection.

What do you think?  Would such a change be acceptable?

Thank you!

Pedro.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help