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>
Junio C Hamano committed
Sep 10, 2005 at 15:23 UTC
b595ed1478e6240593df4c927c4a240575f53d44
1 file changed
+11
-1
Documentation/git-bisect.txt
+11
-1
@@ -13,7 +13,8 @@ SYNOPSIS
13
'git bisect' good <rev>
14
'git bisect' reset [<branch>]
15
'git bisect' visualize
16
-
16
+'git bisect' replay <logfile>
17
+'git bisect' log
18
19
DESCRIPTION
20
-----------
@@ -75,6 +76,15 @@ During the bisection process, you can say
76
77
to see the currently remaining suspects in `gitk`.
78
79
+The good/bad you told the command is logged, and `git bisect
80
+log` shows what you have done so far. You can truncate its
81
+output somewhere and save it in a file, and run
82
+
83
+ git bisect replay that-file
84
+
85
+if you find later you made a mistake telling good/bad about a
86
+revision.
87
+
88
89
Author
90
------