summaryrefslogtreecommitdiffstats
path: root/remote-curl.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2024-07-23 02:04:54 +0200
committerJunio C Hamano <gitster@pobox.com>2024-07-23 17:28:43 +0200
commit728a1962cdaf7df6a1f261dcf3167842cd2db170 (patch)
treee64064ba54556aaa4cf851017c3bb078b87e329a /remote-curl.c
parentYet another batch of post 2.45.2 updates from the 'master' front (diff)
downloadgit-728a1962cdaf7df6a1f261dcf3167842cd2db170.tar.xz
git-728a1962cdaf7df6a1f261dcf3167842cd2db170.zip
CodingGuidelines: document a shell that "fails" "VAR=VAL shell_func"
Over the years, we accumulated the community wisdom to avoid the common "one-short export" construct for shell functions, but seem to have lost on which exact platform it is known to fail. Now during an investigation on a breakage for a recent topic, we found one example of failing shell. Let's document that. This does *not* mean that we can freely start using the construct once Ubuntu 20.04 is retired. But it does mean that we cannot use the construct until Ubuntu 20.04 is fully retired from the machines that matter. Moreover, posix explicitly says that the behaviour for the construct is unspecified. Helped-by: Kyle Lippincott <spectral@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'remote-curl.c')
0 files changed, 0 insertions, 0 deletions