summaryrefslogtreecommitdiff
path: root/t/t6003-rev-list-topo-order.sh
diff options
context:
space:
mode:
authorLibravatar David Tran <unsignedzero@gmail.com>2014-03-18 18:54:05 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-03-19 12:55:57 -0700
commit512477b175288a429aaf4071dc9fe94f17f0e4ee (patch)
tree972f6fa1820571ca7bd2e257f020dd1e1caacb7e /t/t6003-rev-list-topo-order.sh
parentGit 1.9.0 (diff)
downloadtgif-512477b175288a429aaf4071dc9fe94f17f0e4ee.tar.xz
tests: use "env" to run commands with temporary env-var settings
Ordinarily, we would say "VAR=VAL command" to execute a tested command with environment variable(s) set only for that command. This however does not work if 'command' is a shell function (most notably 'test_must_fail'); the result of the assignment is retained and affects later commands. To avoid this, we used to assign and export environment variables and run such a test in a subshell, like so: ( VAR=VAL && export VAR && test_must_fail git command to be tested ) But with "env" utility, we should be able to say: test_must_fail env VAR=VAL git command to be tested which is much shorter and easier to read. Signed-off-by: David Tran <unsignedzero@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t6003-rev-list-topo-order.sh')
0 files changed, 0 insertions, 0 deletions