Johannes Sixt <j.sixt@xxxxxxxxxxxxx> writes: > 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'. Unlike your other message, now, I can see _this_ one making sense very much. It is a very good explanation as to why BISECT_START (whose sole purpose is to go back there) is not a very useful concept. What you wrote deserve to go to the "bisect reset" documentation to explain what the optional <branch> argument (perhaps we would make it a <commit> with Anders's patch) is good for and how it is intended to be used. -- 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