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

Re: rfe: bisecting with a tristate

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
Jul 24, 2007, 21:39 UTC
Message-ID
<200707242339.07980.robin.rosenberg.lists@dewire.com>
In-Reply-To
<Pine.LNX.4.64.0707241818450.14781@racer.site>
tisdag 24 juli 2007 skrev Johannes Schindelin:
> And why exactly do you want to make it hard on the user?
Nah, I don't want to do that. Just thinking aloud ;-)
 
Show 10 quoted lines
> Imagine this history:
> 
> 	A - B - broken - bad - C
> 
> Now you bisect.  It goes to "broken".  You compile.  Darn, does not 
> compile.  Why not have a "git bisect dunno", which considers only the 
> _rest_ of the commits for the next bisection point?  When it finally found 
> the "bad" one, it has to say it broke somewhere between "B..bad".
> 
> Now that would be user friendly, wouldn't it?
It would work fine.
-- robin
Previous: Johannes Schindelin
Message 6 of 6 in “rfe: bisecting with a tristate”
  1. Jan EngelhardtJul 24, 2007
  2. SeanJul 24, 2007
  3. Johannes SchindelinJul 24, 2007
  4. Robin RosenbergJul 24, 2007
  5. Johannes SchindelinJul 24, 2007
  6. Robin RosenbergJul 24, 2007

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.