| commit | 0e418e568f4104ce1915263ae3ad66e290eebed8 | |
| author | Johannes Sixt <j6t@kdbg.org> | |
| Fri, 9 Jul 2010 07:05:16 +0000 (9 09:05 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 9 Jul 2010 23:27:31 +0000 (9 16:27 -0700) | ||
| tree | e929db0b7b2b30d1c9e5003dae01a9c381e01996 | treesnapshot (tar.gz zip) |
| parent | c30e742c4981585061ed52c14abd9ebd32a0e18b | commitdiff |
t0005: work around strange $? in ksh when program terminated by a signal
ksh93 is known to report $? of programs that terminated by a signal as
256 + signal number instead of 128 + signal number like other POSIX
compliant shells (ksh's behavior is still POSIX compliant in this regard).
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
ksh93 is known to report $? of programs that terminated by a signal as
256 + signal number instead of 128 + signal number like other POSIX
compliant shells (ksh's behavior is still POSIX compliant in this regard).
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t0005-signals.sh | diffblobblamehistory |