Hi, > Aaron S. Meurer wrote: >> 90% of the time I do not >> want to go back to where I started bisecting. ÂI would much prefer to just >> have a git bisect stop command [which does "git bisect reset HEAD"] FWIW I like the idea. I end up using "git bisect reset" by accident from time to time and it is almost never what I want, especially after working on something else for a few days[1]. My only worry is that it could be confusing --- what if a person, intending to run "git bisect reset", runs "git bisect stop" instead? To mitigate that, the stop subcommand could print the name of the start commit so such a user knows what to check out to get back to a familiar state. Christian Couder wrote: > Yeah, many people find it difficult to reverse the meaning of "bad" > and "good" when looking for a fix. There were some suggestions at some > points to do something about it. Some of the suggestions were to use > some aliases for "good" and "bad", but there was no agreement. Other > suggestions had a patch attached but the patch was not good enough or > something. Any pointers to such a discussion or patch? Maybe whatever small detail caused it to be forgotten could be fixed... Ciao, Jonathan [1] compare am --abort: http://thread.gmane.org/gmane.comp.version-control.git/164002 -- 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