summaryrefslogtreecommitdiffstats
path: root/t/t4013/diff.format-patch_--inline_--stdout_initial..master^
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2026-04-21 09:34:17 +0200
committerJunio C Hamano <gitster@pobox.com>2026-04-22 15:53:35 -0700
commit9c64add20b09cc47c191c2bc7b2503b02d290385 (patch)
tree4187ab4c2d34c0dc0b76d3697a8448537dde3054 /t/t4013/diff.format-patch_--inline_--stdout_initial..master^
parentf43d01ab90be2711927c8d265b3fb21d2213d2ab (diff)
downloadgit-9c64add20b09cc47c191c2bc7b2503b02d290385.tar.gz
git-9c64add20b09cc47c191c2bc7b2503b02d290385.zip
t: prepare `git config --unset` calls for `set -e`
We have a couple of calls to `git config --unset` that ultimately end up as no-ops as the configuration variables aren't set (anymore) in the first place. These calls are mostly intended to recover unconditionally from tests that may have executed only partially, but they'll ultimately fail during a normal test run. This hasn't been a problem until now as we aren't running tests with `set -e`. This is about to change though, so let's silence the case where we cannot unset the config keys. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4013/diff.format-patch_--inline_--stdout_initial..master^')
0 files changed, 0 insertions, 0 deletions