git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 11, 2017, 14:38 UTC
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:
Show 11 quoted lines
> 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 ;-)

Previous: Christian CouderNext: Theodore Ts'o
Message 3 of 11 in “should "git bisect" support "git bisect next?"”
  1. Robert P. J. DayNov 11, 2017
  2. Christian CouderNov 11, 2017
  3. Junio C HamanoNov 11, 2017
  4. Theodore Ts'oNov 11, 2017
  5. Junio C HamanoNov 12, 2017
  6. Christian CouderNov 12, 2017
  7. Theodore Ts'oNov 12, 2017
  8. Junio C HamanoNov 13, 2017
  9. Robert P. J. DayNov 12, 2017
  10. Junio C HamanoNov 12, 2017
  11. Stephan BeyerNov 12, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.