summaryrefslogtreecommitdiff
path: root/t/t5615-alternate-env.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Sixt <j6t@kdbg.org>2016-11-11 18:31:48 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-11-11 10:54:46 -0800
commit71dd50472d6be8ff91ab0dcfa2413daeaba14baa (patch)
tree35abe97b98396d42b1f3cc71b8efc81763aa3005 /t/t5615-alternate-env.sh
parentMerge branch 'jk/alt-odb-cleanup' (diff)
downloadtgif-71dd50472d6be8ff91ab0dcfa2413daeaba14baa.tar.xz
t0021, t5615: use $PWD instead of $(pwd) in PATH-like shell variables
We have to use $PWD instead of $(pwd) because on Windows the latter would add a C: style path to bash's Unix-style $PATH variable, which becomes confused by the colon after the drive letter. ($PWD is a Unix-style path.) In the case of GIT_ALTERNATE_OBJECT_DIRECTORIES, bash on Windows assembles a Unix-style path list with the colon as separators. It converts the value to a Windows-style path list with the semicolon as path separator when it forwards the variable to git.exe. The same confusion happens when bash's original value is contaminated with Windows style paths. Signed-off-by: Johannes Sixt <j6t@kdbg.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5615-alternate-env.sh')
-rwxr-xr-xt/t5615-alternate-env.sh4
1 files changed, 2 insertions, 2 deletions
diff --git a/t/t5615-alternate-env.sh b/t/t5615-alternate-env.sh
index 22d9d8178b..eec4137ca5 100755
--- a/t/t5615-alternate-env.sh
+++ b/t/t5615-alternate-env.sh
@@ -31,14 +31,14 @@ test_expect_success 'objects inaccessible without alternates' '
'
test_expect_success 'access alternate via absolute path' '
- check_obj "$(pwd)/one.git/objects" <<-EOF
+ check_obj "$PWD/one.git/objects" <<-EOF
$one blob
$two missing
EOF
'
test_expect_success 'access multiple alternates' '
- check_obj "$(pwd)/one.git/objects:$(pwd)/two.git/objects" <<-EOF
+ check_obj "$PWD/one.git/objects:$PWD/two.git/objects" <<-EOF
$one blob
$two blob
EOF