]> git.ipfire.org Git - thirdparty/git.git/commit
projects / thirdparty / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: ab68c70 082caf5)
Merge branch 'pw/submodule-process-sigpipe'
authorJunio C Hamano <gitster@pobox.com>
Mon, 30 Sep 2024 23:16:14 +0000 (16:16 -0700)
committerJunio C Hamano <gitster@pobox.com>
Mon, 30 Sep 2024 23:16:15 +0000 (16:16 -0700)
commit22baac889235bb3752ae36baec36f345871ac939
treec933fdde036ec7033b2237c6f0319170638d2554tree | snapshot
parentab68c70a8b90626be24d95a27f6495ab6e7e57a5commit | diff
parent082caf527ea769635e8c46d0cc181c844c50defdcommit | diff
Merge branch 'pw/submodule-process-sigpipe'

When a subprocess to work in a submodule spawned by "git submodule"
fails with SIGPIPE, the parent Git process caught the death of it,
but gave a generic "failed to work in that submodule", which was
misleading.  We now behave as if the parent got SIGPIPE and die.

* pw/submodule-process-sigpipe:
  submodule status: propagate SIGPIPE
builtin/submodule--helper.c diff1 | diff2 | blob | history
Unnamed repository; edit this file 'description' to name the repository.