Johannes Sixt <j.sixt@xxxxxxxxxxxxx> writes: > In my workflow, after I've found the bad commit, I always want bisect to > stay at the commit that it found. I don't want it to warp me somewhere > else; I want to make the decision where to go next myself. Are you sure about what you are saying? Half of the time, the commit you test in your "git bisect" section would be a "good" one, and immediately after you tell it "bisect good", it tells you that some _other_ commit you marked "bad" is the first bad commit. In such a case, you won't be on the commit that the bisect has found. So I _do_ agree that you would always want to stare at the commit that is the first bad one, leaving the bisection session at the detached HEAD state bisection session ends at is _totally_ different from what you want. -- 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