From b595ed1478e6240593df4c927c4a240575f53d44 Mon Sep 17 00:00:00 2001
From: Junio C Hamano <junkio@cox.net>
Date: Sat, 10 Sep 2005 15:23:09 -0700
Subject: 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 ae43876..f10df53 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
 ------
-- 
cgit v0.10.2-6-g49f6