{"thread":{"id":"32867","subject":"Wishlist: git help bisect should mention \"stop\" keyword","startedAt":"2013-02-09T08:44:03Z","lastAt":"2013-02-09T08:44:03Z","messageCount":1,"participants":["Andreas Mohr"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"209075","messageId":"20130209084403.GA14356@rhlx01.hs-esslingen.de","threadId":"32867","inReplyTo":null,"subject":"Wishlist: git help bisect should mention \"stop\" keyword","fromName":"Andreas Mohr","fromEmail":"andi@lisas.de","sentAt":"2013-02-09T08:44:03Z","receivedAt":"2013-02-09T08:44:03Z","isPatch":false,"sender":{"key":"andi@lisas.de","avatar":null},"body":"Hi,\n\nthe man page (git version 1.7.10.4) is a bit non-symmetric\nsince git bisect has the start param, but when searching for \"stop\"\n(nothing more obvious than that, right?),\none comes up empty --> usability issue.\n\nThe appropriate action complementary to start appears to be\ngit bisect reset, thus its description definitely ought to include a \"stop\"\nkeyword.\n\nDescription as of 1.7.10.4 is\n\n       After a bisect session, to clean up the bisection state and\nreturn to\n       the original HEAD, issue the following command:\n\n           $ git bisect reset\n\nwhich could be changed into\n\n       After a bisect session, to clean up the bisection state and\nreturn to\n       the original HEAD (in other words, to \"stop\" bisect),\n       issue the following command:\n\n           $ git bisect reset\n\nAndreas Mohr\n\n-- \nGNU/Linux. It's not the software that's free, it's you.\n"}]}