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>

diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index ae438761b258b805313b2ec8e55dc4ac19405b60..f10df535a5b31d195bd53b46c460ec0891f1d0ea 100644 (file)
--- 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' good <rev>
 'git bisect' reset [<branch>]
 'git bisect' visualize

-
+'git bisect' replay <logfile>
+'git bisect' log

 
 DESCRIPTION
 -----------
 
 DESCRIPTION
 -----------


@@ -75,6 +76,15 @@ During the bisection process, you can say
 
 to see the currently remaining suspects in `gitk`.
 
 
 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
 ------
 
 Author
 ------