bisect: explain the rationale behind 125
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Mar 19, 2011 at 21:46 UTC
958bf6b768aa10fa3985886d312bd0365dee7677
1 file changed
+6
-1
Documentation/git-bisect.txt
+6
-1
@@ -241,7 +241,12 @@ exit(3) manual page), as the value is chopped with "& 0377".
241
242
The special exit code 125 should be used when the current source code
243
cannot be tested. If the script exits with this code, the current
244
-revision will be skipped (see `git bisect skip` above).
244
+revision will be skipped (see `git bisect skip` above). 125 was chosen
245
+as the highest sensible value to use for this purpose, because 126 and 127
246
+are used by POSIX shells to signal specific error status (127 is for
247
+command not found, 126 is for command found but not executable---these
248
+details do not matter, as they are normal errors in the script, as far as
249
+"bisect run" is concerned).
250
251
You may often find that during a bisect session you want to have
252
temporary modifications (e.g. s/#define DEBUG 0/#define DEBUG 1/ in a