summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-08-30 12:45:41 -0700
committerJunio C Hamano <junkio@cox.net>2005-08-30 12:45:41 -0700
commitcc9f24d024e7e4bf0b2fbd4e1beb7eb1a425805f (patch)
treede2a595537e758e6fd9a8a0a18e2e1b1bae8022a /README
parent670f5fe34f0f6a363297d5dcd73051089b78fe82 (diff)
downloadgit-cc9f24d024e7e4bf0b2fbd4e1beb7eb1a425805f.tar.gz
'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>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions