summaryrefslogtreecommitdiff
path: root/Documentation/git-bisect.txt
diff options
context:
space:
mode:
authorChristian Couder <chriscool@tuxfamily.org>2007-03-24 05:29:58 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-03-24 06:25:54 (GMT)
commit7891a2811dc7cae375e34c9f4fa6c8ecaef0f6d7 (patch)
treed22b505b0ef5e3929c158609372ab645e079891b /Documentation/git-bisect.txt
parenta4e9d71edb5f87b4dae57b8a474124451e397e6c (diff)
downloadgit-7891a2811dc7cae375e34c9f4fa6c8ecaef0f6d7.zip
git-7891a2811dc7cae375e34c9f4fa6c8ecaef0f6d7.tar.gz
git-7891a2811dc7cae375e34c9f4fa6c8ecaef0f6d7.tar.bz2
Documentation: bisect: reformat some paragraphs.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/git-bisect.txt')
-rw-r--r--Documentation/git-bisect.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index b7cd715..a77fbe8 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -122,17 +122,17 @@ like this:
$ git bisect start arch/i386 include/asm-i386
------------
-If you have a script that can tell if the current
-source code is good or bad, you can automatically bisect using:
+If you have a script that can tell if the current source code is good
+or bad, you can automatically bisect using:
------------
$ git bisect run my_script
------------
-Note that the "run" script (`my_script` in the above example)
-should exit with code 0 in
-case the current source code is good and with a code between 1 and 127
-(included) in case the current source code is bad.
+Note that the "run" script (`my_script` in the above example) should
+exit with code 0 in case the current source code is good and with a
+code between 1 and 127 (included) in case the current source code is
+bad.
Any other exit code (a program that does "exit(-1)" leaves $? = 255,
see exit(3) manual page, the value is chopped with "& 0377") will