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

Re: Bisection visualization hint..

From
Junio C Hamano <junkio@cox.net>
Date
Aug 30, 2005, 17:47 UTC
Message-ID
<7vhdd7joz6.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.58.0508301026450.4293@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
Show 8 quoted lines
> I'm testing bisection to find a bug that causes my G5 to no longer boot, 
> and during the process have found this command line very nice:
>
> 	gitk bisect/bad --not $(cd .git/refs ; ls bisect/good-*)
>
> it basically shows the state of bisection with the known bad commit as the 
> top, and cutting off all the good commits - so what you see are the 
> potential buggy commits.
Show 6 quoted lines
> But it's not the nicest of command lines and depends on knowing how
> bisection works, so maybe we could make
>
> 	git bisect visualize
>
> do this for us?
Will do.

Another thing that might make sense is roll it also into gitk, a new command from "File" menu to cause it to re-read not just ref values but the rev-list itself out of that particular rev-list command (and add any other common patterns as we discover them).

Previous: Linus TorvaldsNext: A Large Angry SCM
Message 2 of 7 in “Bisection visualization hint..”
  1. Linus TorvaldsAug 30, 2005
  2. Junio C HamanoAug 30, 2005
  3. A Large Angry SCMAug 30, 2005
  4. Linus TorvaldsAug 30, 2005
  5. Fix bisection terminating conditionLinus Torvalds, Aug 30, 2005
  6. Junio C HamanoAug 30, 2005
  7. 'git bisect visualize'Junio C Hamano, Aug 30, 2005

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.