Linus Torvalds [off-list ref] 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).
Junio C Hamano wrote:
Linus Torvalds [off-list ref] writes:
quoted
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.
quoted
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.
On Tue, 30 Aug 2005, A Large Angry SCM wrote:
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.
I really think that gitk is pretty fundamental. If for no other reason
than the big fact that it helps people understand what is going on. That's
why it's mentioned in the tutorial - people who have only used something
broken like CVS will have a hard time visualizing what's going on, I
suspect, but with gitk it all looks simple.
Linus