Hi, On 11/11/2017 03:38 PM, Junio C Hamano wrote: > Christian Couder <christian.cou...@gmail.com> writes: > >> On Sat, Nov 11, 2017 at 12:42 PM, Robert P. J. Day >> <rpj...@crashcourse.ca> wrote: >>> >>> the man page for "git bisect" makes no mention of "git bisect next", >>> but the script git-bisect.sh does: >> >> Yeah the following patch was related: >> >> https://public-inbox.org/git/1460294354-7031-2-git-send-email-s-be...@gmx.net/ >> >> You might want to discuss with Stephan (cc'ed). > > Thanks for saving me time to explain why 'next' is still a very > important command but the end users do not actually need to be > strongly aware of it, because most commands automatically invokes it > as their final step due to the importance of what it does ;-)
I will nonetheless re-roll the patch (that Christian linked to) after Pranit's bisect part II series is in good shape. I think the documentation change in the patch shows why the user should be aware of it (although not strongly). Best Stephan
