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

Re: Bisects that are neither good nor bad

From
Linus Torvalds <torvalds@osdl.org>
Date
May 30, 2006, 00:46 UTC
Message-ID
<Pine.LNX.4.64.0605291744390.5623@g5.osdl.org>
In-Reply-To
<20060529225632.7073.qmail@science.horizon.com>
On Mon, 29 May 2006, linux@horizon.com wrote:
Show 8 quoted lines
> 
> It's also worth repeating some advice from the manual:
> 
> >> You can further cut down the number of trials if you know what part of
> >> the tree is involved in the problem you are tracking down, by giving
> >> paths parameters when you say bisect start, like this:
> >>
> >> $ git bisect start arch/i386 include/asm-i386

I'm not 100% sure this works - I think it has problems with the ending condition because there always ends up being more commits in between when the commit space isn't dense, so the "no commits left" thing doesn't trigger. But "git bisect visualize" should hopefully help make it obvious

		Linus
Previous: linux@horizon.com
Message 2 of 2 in “Re: Bisects that are neither good nor bad”
  1. linux@horizon.comMay 29, 2006
  2. Linus TorvaldsMay 30, 2006

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.