summaryrefslogtreecommitdiff
path: root/Documentation/technical
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-01-11 18:34:32 -0800
committerJunio C Hamano <gitster@pobox.com>2013-01-11 18:34:32 -0800
commitedb6ad5b0aa7152dc230c0e75f14fb41b8302db4 (patch)
tree4171bb3c75d9fa06a9f053a276869c64ccf302c3 /Documentation/technical
parentc566ea13fd25be8a7c20bdf3644d1ebe3f65b690 (diff)
parent709ca730f8e093005cc882bfb86c0ca9c83d345b (diff)
downloadgit-edb6ad5b0aa7152dc230c0e75f14fb41b8302db4.tar.gz
Merge branch 'jk/unify-exit-code-by-receiving-signal'
The internal logic had to deal with two representations of a death of a child process by a signal. * jk/unify-exit-code-by-receiving-signal: run-command: encode signal death as a positive integer
Diffstat (limited to 'Documentation/technical')
-rw-r--r--Documentation/technical/api-run-command.txt6
1 files changed, 2 insertions, 4 deletions
diff --git a/Documentation/technical/api-run-command.txt b/Documentation/technical/api-run-command.txt
index f18b4f4817..5d7d7f2d32 100644
--- a/Documentation/technical/api-run-command.txt
+++ b/Documentation/technical/api-run-command.txt
@@ -55,10 +55,8 @@ The functions above do the following:
non-zero.
. If the program terminated due to a signal, then the return value is the
- signal number - 128, ie. it is negative and so indicates an unusual
- condition; a diagnostic is printed. This return value can be passed to
- exit(2), which will report the same code to the parent process that a
- POSIX shell's $? would report for a program that died from the signal.
+ signal number + 128, ie. the same value that a POSIX shell's $? would
+ report. A diagnostic is printed.
`start_async`::