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

Re: bisect and gitk happy together

From
Linus Torvalds <torvalds@osdl.org>
Date
Jun 12, 2006, 15:10 UTC
Message-ID
<Pine.LNX.4.64.0606120807350.5498@g5.osdl.org>
In-Reply-To
<46a038f90606120441p74dd4872y441fe04470f4acd5@mail.gmail.com>
On Mon, 12 Jun 2006, Martin Langhoff wrote:
> 
> - git-bisect visualise wasn't as useful as just a plain gitk. (This
> may be because I was working with ~60 commits in a medium-sized
> project).

Definitely. Try just firing up gitk when you're bisecting a kernel archive with thousands of commits, and complex history..

That's when "git bisect visualize" really helps: when git bisect has already narrowed down the list of commits from "5 years" to "1 week", but you still have maybe a hundred-odd commits to go.

I agree that just plain "gitk" is actually nicer if you want to see the whole context. It's just that often the context is pretty damn confusing ;)

> - gitk didn't show the bad commit tagged specially, even if
> git-bisect had just identified it. Of course I could find it, but I
> had all the other good/bad commits well labelled. And not the one I
> was looking for. Odd.

It should be the head of the "bisect" branch, and naturally tagged that way.

			Linus
Previous: Martin Langhoff
Message 2 of 2 in “bisect and gitk happy together”
  1. Martin LanghoffJun 12, 2006
  2. Linus TorvaldsJun 12, 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.