summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2021-05-03 05:23:24 (GMT)
committerJunio C Hamano <gitster@pobox.com>2021-05-03 05:24:11 (GMT)
commita84fd3bcc6253f847af3366ebb9de9b8f441a624 (patch)
tree09134175ef27c215bcd7cdafa70964e392086927 /t
parent48bf2fa8bad054d66bd79c6ba903c89c704201f7 (diff)
downloadgit-a84fd3bcc6253f847af3366ebb9de9b8f441a624.zip
git-a84fd3bcc6253f847af3366ebb9de9b8f441a624.tar.gz
git-a84fd3bcc6253f847af3366ebb9de9b8f441a624.tar.bz2
CodingGuidelines: explicitly allow "local" for test scripts
01d3a526 (t0000: check whether the shell supports the "local" keyword, 2017-10-26) raised a test balloon to see if those who build and test Git use a platform with a shell that lacks support for the "local" keyword. After two years, 7f0b5908 (t0000: reword comments for "local" test, 2019-08-08) documented that "local" keyword, even though is outside POSIX, is allowed in our test scripts. Let's write it in the CodingGuidelines, too. It might be tempting to allow it in scripted Porcelains (we have avoided getting them contaminiated by "local" so far), but they are on their way out and getting rewritten in C. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't')
0 files changed, 0 insertions, 0 deletions