From: Junio C Hamano <gitster@pobox.com>
Date: Sat, 11 Nov 2017 14:38:23 GMT
Subject: Re: should "git bisect" support "git bisect next?"
Message-ID: <xmqq4lq0ev8g.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAP8UFD3az17BpB0nA+35p3BP95sBuOY0Yvce3cgbh0L3YH7+rQ@mail.gmail.com>

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 ;-)