summaryrefslogtreecommitdiff
path: root/Documentation/howto/new-command.txt
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2016-11-27 01:34:45 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-11-29 11:00:38 -0800
commitfa3142c9193bb31e7154d0f0cd7d15208a8dd51a (patch)
tree3c283a2df4c0f19169b684c2d8815a7142b7aef8 /Documentation/howto/new-command.txt
parentt7610: test for mktemp before test execution (diff)
downloadtgif-fa3142c9193bb31e7154d0f0cd7d15208a8dd51a.tar.xz
t7610: clean up foo.XXXXXX tmpdir
The lazy prereq for MKTEMP uses "mktemp -t" to see if mergetool's internal mktemp call will be able to run. But unlike the call inside mergetool, we do not ever bother to clean up the result, and the /tmp of git developers will slowly fill up with "foo.XXXXXX" directories as they run the test suite over and over. Let's clean up the directory after we've verified its creation. Note that we don't use test_when_finished here, and instead just make rmdir part of the &&-chain. We should only remove something that we're confident we just created. A failure in the middle of the chain either means there's nothing to clean up, or we are very confused and should err on the side of caution. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/howto/new-command.txt')
0 files changed, 0 insertions, 0 deletions