aboutsummaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2012-07-30 13:04:18 -0700
committerJunio C Hamano <gitster@pobox.com>2012-07-30 13:04:18 -0700
commit8ba105dda861d33f3d7c3b9989592c1605027116 (patch)
tree1803040c3b7b69d3d5b9e8453cf79524f11af487 /t
parent80ffb7570f86fb8b671048a374f3c7990c45a27f (diff)
parent6eafa6d096ce6b0ae20e4c0fbb248958559daf64 (diff)
downloadgit-8ba105dda861d33f3d7c3b9989592c1605027116.tar.gz
git-8ba105dda861d33f3d7c3b9989592c1605027116.tar.xz
Merge branch 'jl/maint-1.7.10-recurse-submodules-with-symlink' into maint
When "git submodule add" clones a submodule repository, it can get confused where to store the resulting submodule repository in the superproject's .git/ directory when there is a symbolic link in the path to the current directory. * jl/maint-1.7.10-recurse-submodules-with-symlink: submodules: don't stumble over symbolic links when cloning recursively
Diffstat (limited to 't')
-rwxr-xr-xt/t7406-submodule-update.sh13
1 files changed, 13 insertions, 0 deletions
diff --git a/t/t7406-submodule-update.sh b/t/t7406-submodule-update.sh
index dcb195b4c..ce61d4c0f 100755
--- a/t/t7406-submodule-update.sh
+++ b/t/t7406-submodule-update.sh
@@ -636,4 +636,17 @@ test_expect_success 'submodule update properly revives a moved submodule' '
)
'
+test_expect_success SYMLINKS 'submodule update can handle symbolic links in pwd' '
+ mkdir -p linked/dir &&
+ ln -s linked/dir linkto &&
+ (
+ cd linkto &&
+ git clone "$TRASH_DIRECTORY"/super_update_r2 super &&
+ (
+ cd super &&
+ git submodule update --init --recursive
+ )
+ )
+'
+
test_done