On Sun, Jun 23, 2019 at 01:32:16PM -0700, Pedro Larroy wrote: > Thanks for your answer. > > I was expecting the HEAD to point to the first bad commit. > > In mercurial, the exit status tells you information about the > bisection process: https://www.mercurial-scm.org/repo/hg/help/bisect > > Sure one can parse stdout, it's just more tedious than just checking > the return code and having the HEAD left to the original bad commit. I think it might be nice for Git to write a well-known refname (like BISECT_RESULT or similar) so that you can refer to that instead of having to read stdout (whether by machine or by a user cutting-and-pasting). And I cannot offhand think of a particular reason why that could not just be HEAD (instead of something bisect-specific) after the bisect finishes. We do not promise any particular value in HEAD now. The only downside would be the minor cost to checkout the working tree of the known-bad commit if we are not already there. -Peff
