summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Denton Liu <liu.denton@gmail.com>2019-11-27 11:53:20 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-11-29 13:20:14 -0800
commit50cd31c6526637e59ca180397aba425ec7a1e218 (patch)
tree501005f29e44f708e25b7a35f536944504470c97
parentt3600: stop losing return codes of git commands (diff)
downloadtgif-50cd31c6526637e59ca180397aba425ec7a1e218.tar.xz
t3600: comment on inducing SIGPIPE in `git rm`
Add a comment about intentionally inducing SIGPIPE since this is unusual and future developers should be aware. Also, even though we are trying to refactor git commands out of the upstream of pipes, we cannot do it here since we rely on it being upstream to induce SIGPIPE. Comment on that as well so that future developers do not try to change it. Signed-off-by: Denton Liu <liu.denton@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rwxr-xr-xt/t3600-rm.sh1
1 files changed, 1 insertions, 0 deletions
diff --git a/t/t3600-rm.sh b/t/t3600-rm.sh
index 0c3bf10edd..0ea858d652 100755
--- a/t/t3600-rm.sh
+++ b/t/t3600-rm.sh
@@ -251,6 +251,7 @@ test_expect_success 'choking "git rm" should not let it die with cruft' '
echo "100644 $hash 0 some-file-$i"
i=$(( $i + 1 ))
done | git update-index --index-info &&
+ # git command is intentionally placed upstream of pipe to induce SIGPIPE
git rm -n "some-file-*" | : &&
test_path_is_missing .git/index.lock
'