Re: should "git bisect" support "git bisect next?"

From: Stephan Beyer <s-beyer@gmx.net>
Date: Nov 12, 2017, 20:08 UTC
Message-ID: <cc11ab35-a219-8cab-313e-f716723409e4@gmx.net>
In-Reply-To: <xmqq4lq0ev8g.fsf@gitster.mtv.corp.google.com>

Hi,

On 11/11/2017 03:38 PM, Junio C Hamano wrote:

Show 18 quoted lines

> Christian Couder <christian.couder@gmail.com> writes:
> 
>> On Sat, Nov 11, 2017 at 12:42 PM, Robert P. J. Day
>> <rpjday@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-beyer@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