[PATCH] Documentation: "bisect run" can be given bangs before the run script.

From

Christian Couder <chriscool@tuxfamily.org>

Date

May 3, 2007, 05:06 UTC

Message-ID

<20070503070607.fa2ffe92.chriscool@tuxfamily.org>

Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---

Hi Uwe and Junio,

This is the documentation related to my latest patch:

[RFC/PATCH] Bisect: add special treatment for bangs passed to "bisect run".

(http://article.gmane.org/gmane.comp.version-control.git/45943)

 Documentation/git-bisect.txt |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index 5f68ee1..a1cceb5 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -175,6 +175,12 @@ Any other exit code will abort the automatic bisect process. (A
 program that does "exit(-1)" leaves $? = 255, see exit(3) manual page,
 the value is chopped with "& 0377".)
 
+You can use one or more "!" argument immediately after "git bisect
+run" if you want to revert once or more times the "run" script exit
+code, even if your current shell does not support the "!"
+keyword. Reverting the exit code means 0 gives 1 and anything other
+than 0 gives 0.
+
 You may often find that during bisect you want to have near-constant
 tweaks (e.g., s/#define DEBUG 0/#define DEBUG 1/ in a header file, or
 "revision that does not have this commit needs this patch applied to

-- 
1.5.2.rc0.71.g4342-dirty