aboutsummaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-09-10 15:23:09 -0700
committerJunio C Hamano <junkio@cox.net>2005-09-10 15:23:09 -0700
commitb595ed1478e6240593df4c927c4a240575f53d44 (patch)
treee0b3076650952676a07ee72f9b0492639762aeec /Documentation
parente204de28e69617265e88c73dd13c416ffa15f355 (diff)
downloadgit-b595ed1478e6240593df4c927c4a240575f53d44.tar.gz
git-b595ed1478e6240593df4c927c4a240575f53d44.tar.xz
Add 'git bisect replay/log' documentation.
... lest I get yelled at by a very angry scm ;-). Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-bisect.txt12
1 files changed, 11 insertions, 1 deletions
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index ae438761b..f10df535a 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -13,7 +13,8 @@ SYNOPSIS
'git bisect' good <rev>
'git bisect' reset [<branch>]
'git bisect' visualize
-
+'git bisect' replay <logfile>
+'git bisect' log
DESCRIPTION
-----------
@@ -75,6 +76,15 @@ During the bisection process, you can say
to see the currently remaining suspects in `gitk`.
+The good/bad you told the command is logged, and `git bisect
+log` shows what you have done so far. You can truncate its
+output somewhere and save it in a file, and run
+
+ git bisect replay that-file
+
+if you find later you made a mistake telling good/bad about a
+revision.
+
Author
------