Re: Bisection visualization hint..

From: A Large Angry SCM <gitzilla@gmail.com>
Date: Aug 30, 2005, 18:03 UTC
Message-ID: <43149F79.4020809@gmail.com>
In-Reply-To: <7vhdd7joz6.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

Show 24 quoted lines

> Linus Torvalds <torvalds@osdl.org> writes:
> 
>>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.
> 
>>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).

Unless gitk will always be part of git, this is better off as a gitk feature or gitk helper script. IE. it belongs in the gitk namespace, not the git namespace.

That said, a wrapper for "git show-branch" (git show-bisect?) would be nice also.