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

Re: git bisect enhancement request

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Aug 14, 2020, 22:08 UTC
Message-ID
<20200814220828.GP8085@camp.crustytoothpaste.net>
In-Reply-To
<CAJfuBxw2KudBPfpmVqU9VOfnvrKdczU6Us5FWvpj50T88BarHw@mail.gmail.com>
On 2020-08-14 at 21:11:19, jim.cromie@gmail.com wrote:
> please teach git bisect how to use 2 separate worktrees
> for the bisection, toggling between them as bisection progresses,
> so that the end result is 2 compiled kernels,
> one broken, one good.

I'm not sure how such a thing would be implemented. Git doesn't know until after it's checked out the tree whether a revision is good or bad, since usually the user needs to tell it (or use git bisect run). Even if Git alternated between the two worktrees in order, that doesn't mean that one of them will end up being good, since Git may find the last good revision early on, then continue to bisect and find many bad revisions until it determines the right one.

Can you tell us more about the algorithm you'd like to see here?
-- 
brian m. carlson: Houston, Texas, US
Previous: jim.cromie@gmail.comNext: Randall S. Becker
Message 2 of 5 in “git bisect enhancement request”
  1. jim.cromie@gmail.comAug 14, 2020
  2. brian m. carlsonAug 14, 2020
  3. Randall S. BeckerAug 14, 2020
  4. jim.cromie@gmail.comAug 15, 2020
  5. Randall S. BeckerAug 15, 2020

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.