aboutsummaryrefslogtreecommitdiffstats
path: root/erl-build-tool-vars.sh
diff options
context:
space:
mode:
authorErlang/OTP <[email protected]>2010-05-04 08:50:40 +0000
committerErlang/OTP <[email protected]>2010-05-04 08:50:40 +0000
commit33e2df7148957f2be1cb12f0302ac80034b8ad22 (patch)
treeb784eeed4e376d440f4ad53fa21ff02c4525a58b /erl-build-tool-vars.sh
parent06ed4aab7ec48399a55323f0f605ba96db6d407f (diff)
parent6f40c6686d5e94aa2cead2739f61a45c594a7d6a (diff)
downloadotp-33e2df7148957f2be1cb12f0302ac80034b8ad22.tar.gz
otp-33e2df7148957f2be1cb12f0302ac80034b8ad22.tar.bz2
otp-33e2df7148957f2be1cb12f0302ac80034b8ad22.zip
Merge branch 'sv/env-with-equal-sign' into dev
* sv/env-with-equal-sign: allow open_port to set env vars containing a trailing '=' character OTP-8614 sv/env-with-equal-sign The erlang:open_port spawn and spawn_executable directives can include an {env,Env} directive to set up environment variables for the spawned process. A bug prevented applications from using {env,Env} to set an environment variable whose value ended with a '=' (equal sign) character; the trailing equal sign was mistaken as an indication that an environment variable was to be cleared from the environment of the spawned process. (Thanks to Steve Vinoski.)
Diffstat (limited to 'erl-build-tool-vars.sh')
0 files changed, 0 insertions, 0 deletions