![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Junio C Hamano <junkio@cox.net> | |
| Tue, 30 Aug 2005 19:45:41 +0000 (12:45 -0700) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Tue, 30 Aug 2005 19:45:41 +0000 (12:45 -0700) | ||
| commit | cc9f24d024e7e4bf0b2fbd4e1beb7eb1a425805f | |
| tree | de2a595537e758e6fd9a8a0a18e2e1b1bae8022a | tree | snapshot |
| parent | 670f5fe34f0f6a363297d5dcd73051089b78fe82 | commit | diff |
'git bisect visualize'
Linus says:
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.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Linus says:
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.
Signed-off-by: Junio C Hamano <junkio@cox.net>
| git-bisect-script | diff | blob | history |