Junio C Hamano schrieb: > I would understand it, if not agreeing that I also am often in that > situation myself", if somebody does not even care which commit he was on > before starting the bisection, but knows (or is willing to decide at that > point) which branch (or even a specific commit, while still being > detached) he wants to switch to. And it would make sense to avoid an > extra checkout that snaps back to the pre-bisection commit before > switching to the new state he has chosen. The situation that I'm faced quite frequently is that after I find a regression, I cannot tell which released version did not have the breakage. Hence, the first thing I have to do is to find a good commit. Therefore, I jump around in ancient history until I find a good commit. Then I start bisect. I certainly do NOT want to be warped back to this ancient commit by 'bisect reset'. -- Hannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html