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

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

From
Theodore Ts'o <tytso@mit.edu>
Date
Nov 11, 2017, 19:46 UTC
Message-ID
<20171111194616.a2hl4dwz5cycuzdh@thunk.org>
In-Reply-To
<xmqq4lq0ev8g.fsf@gitster.mtv.corp.google.com>
On Sat, Nov 11, 2017 at 11:38:23PM +0900, Junio C Hamano wrote:
Show 5 quoted lines
> 
> 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 ;-)

This reminds me; is there a way to suppress it because I'm about to give a large set of good and bit commits (perhaps because I'm replaying part of a git biset log, minus one or two lines that are suspected of being bogus thanks to flaky reproduction), and so there's no point having git bisect figure the "next" commit to try until I'm done giving it a list of good/bad commits?

	     	       	      	 	  - Ted
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 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.