path: root/Documentation/git-bisect.txt
diff options
authorJunio C Hamano <>2007-12-07 10:25:34 (GMT)
committerJunio C Hamano <>2007-12-08 10:58:26 (GMT)
commit235997c90fe8648ac199f9a1ae257e06c145c131 (patch)
tree6cae03a2e140b2724381220975ee94fc5041f922 /Documentation/git-bisect.txt
parent4af756f31b0696ed1ca6ad10dc6d7053477edc16 (diff)
git-bisect visualize: work in non-windowed environments better
This teaches "git bisect visualize" to be more useful in non-windowed environments. (1) When no option is given, and $DISPLAY is set, it continues to spawn gitk as before; (2) When no option is given, and $DISPLAY is unset, "git log" is run to show the range of commits between the bad one and the good ones; (3) If only "-flag" options are given, "git log <options>" is run. E.g. "git bisect visualize --stat" (4) Otherwise, all of the given options are taken as the initial part of the command line and the commit range expression is given to that command. E.g. "git bisect visualize tig" will run "tig" history viewer to show between the bad one and the good ones. As "visualize" is a bit too long to type, we also give it a shorter synonym "view". Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-bisect.txt')
1 files changed, 10 insertions, 1 deletions
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index 4795349..8b9d61a 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -92,7 +92,16 @@ During the bisection process, you can say
$ git bisect visualize
-to see the currently remaining suspects in `gitk`.
+to see the currently remaining suspects in `gitk`. `visualize` is a bit
+too long to type and `view` is provided as a synonym.
+If `DISPLAY` environment variable is not set, `git log` is used
+instead. You can even give command line options such as `-p` and
+$ git bisect view --stat
Bisect log and bisect replay