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

Feature request: don't require both bad and good when bisecting

From
Ddarxus@chaosreigns.com <darxus@chaosreigns.com>
Date
Mar 18, 2012, 21:29 UTC
Message-ID
<20120318212957.GS1219@chaosreigns.com>

I'd like to be able to tell get only that I know the latest commit is bad, and have it go find a good commit, then do the bisecting. Maybe something like the opposite of a binary search, start with the last commit, then second to last, then 4th to last, 8th to last, etc., till it finds a good commit.

-- 
"This hurts quite a bit. Very painful."
"Think of the sensation as reassurance that you are not dead yet. What
you are feeling is life in you!" - Johnny The Homicidal Maniac
http://www.ChaosReigns.com
Next: Andreas Ericsson
Message 1 of 6 in “Feature request: don't require both bad and good when bisecting”
  1. darxus@chaosreigns.comMar 18, 2012
  2. Andreas EricssonMar 19, 2012
  3. Jeff KingMar 19, 2012
  4. Andreas EricssonMar 19, 2012
  5. Jeff KingMar 19, 2012
  6. Junio C HamanoMar 19, 2012

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.