summaryrefslogtreecommitdiff
path: root/Documentation/git-remote-fd.txt
diff options
context:
space:
mode:
authorLibravatar Johannes Sixt <j6t@kdbg.org>2016-07-22 21:14:38 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-07-22 13:43:50 -0700
commitc4c02bf16c47f8751958458e540269ec13f4bd98 (patch)
tree174e1e867fd15445abe2d4ee8f23145257b3c5b0 /Documentation/git-remote-fd.txt
parentMerge branch 'sb/submodule-clone-retry' (diff)
downloadtgif-c4c02bf16c47f8751958458e540269ec13f4bd98.tar.xz
git-submodule: forward exit code of git-submodule--helper more faithfully
git-submodule--helper is invoked as the upstream of a pipe in several places. Usually, the failure of a program in this position is not detected by the shell. For this reason, the code inserts a token in the output stream when git-submodule--helper fails that is detected downstream, where the shell script is quit with exit code 1. There happens to be a bug in git-submodule--helper that leads to a segmentation fault. The test suite triggers the crash in several places, all of which are protected by 'test_must_fail'. But due to the inspecific exit code 1, the crash remains undiagnosed. Extend the failure protocol such that git-submodule--helper's exit code is passed downstream (only in the case of failure). This enables the downstream to use it as its own exit code, and 'test_must_fail' to identify the segmentation fault as an unexpected failure. The bug itself is fixed in the next commit. Signed-off-by: Johannes Sixt <j6t@kdbg.org> Acked-by: Stefan Beller <sbeller@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-remote-fd.txt')
0 files changed, 0 insertions, 0 deletions