| commit | e8189ee90e65094dd46a9e4ee6455d9efa90fa76 | |
| author | Tarmigan Casebolt <tarmigan+git@gmail.com> | |
| Fri, 15 Jan 2010 06:44:02 +0000 (14 22:44 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sat, 16 Jan 2010 05:05:35 +0000 (15 21:05 -0800) | ||
| tree | 1ae61ecefd5caacd85c2d4aa3bf002b143d08b5f | treesnapshot (tar.gz zip) |
| parent | fd0a8c2e6428acb883bf4707de54b3e026c57455 | commitdiff |
Test t5560: Fix test when run with dash
A command invocation preceded by variable assignments, i.e.
VAR1=VAL1 VAR2=VAL2 ... command args
are implemented by dash and ksh in such a way not to export these
variables, and keep the values after the command finishes, when the
command is a shell function. POSIX.1 "2.9.5 Function Definition Command"
specifies this behaviour.
Many shells however treat this construct the same way as they are calling
external commands. They export the variables during the duration of
command, and resets their values after command returns.
The test relied on the behaviour of the latter kind.
Reported-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Tarmigan Casebolt <tarmigan+git@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
A command invocation preceded by variable assignments, i.e.
VAR1=VAL1 VAR2=VAL2 ... command args
are implemented by dash and ksh in such a way not to export these
variables, and keep the values after the command finishes, when the
command is a shell function. POSIX.1 "2.9.5 Function Definition Command"
specifies this behaviour.
Many shells however treat this construct the same way as they are calling
external commands. They export the variables during the duration of
command, and resets their values after command returns.
The test relied on the behaviour of the latter kind.
Reported-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Tarmigan Casebolt <tarmigan+git@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t5560-http-backend-noserver.sh | diffblobblamehistory |