3 test_description
='pulling from symlinked subdir'
5 TEST_PASSES_SANITIZE_LEAK
=true
8 # The scenario we are building:
14 # subdir-link -> clone-repo/subdir/
16 # The working directory is subdir-link.
18 test_expect_success SYMLINKS setup
'
20 echo file >subdir/file &&
21 git add subdir/file &&
22 git commit -q -m file &&
23 git clone -q . clone-repo &&
24 ln -s clone-repo/subdir/ subdir-link &&
27 git config receive.denyCurrentBranch warn
29 git config receive.denyCurrentBranch warn
32 # Demonstrate that things work if we just avoid the symlink
34 test_expect_success SYMLINKS
'pulling from real subdir' '
36 echo real >subdir/file &&
37 git commit -m real subdir/file &&
38 cd clone-repo/subdir/ &&
40 test real = $(cat file)
44 # From subdir-link, pulling should work as it does from
47 # Instead, the error pull gave was:
49 # fatal: 'origin': unable to chdir or not a git archive
50 # fatal: The remote end hung up unexpectedly
52 # because git would find the .git/config for the "trash directory"
53 # repo, not for the clone-repo repo. The "trash directory" repo
54 # had no entry for origin. Git found the wrong .git because
55 # git rev-parse --show-cdup printed a path relative to
56 # clone-repo/subdir/, not subdir-link/. Git rev-parse --show-cdup
57 # used the correct .git, but when the git pull shell script did
58 # "cd $(git rev-parse --show-cdup)", it ended up in the wrong
59 # directory. A POSIX shell's "cd" works a little differently
60 # than chdir() in C; "cd -P" is much closer to chdir().
62 test_expect_success SYMLINKS
'pulling from symlinked subdir' '
64 echo link >subdir/file &&
65 git commit -m link subdir/file &&
68 test link = $(cat file)
72 # Prove that the remote end really is a repo, and other commands
73 # work fine in this context. It's just that "git pull" breaks.
75 test_expect_success SYMLINKS
'pushing from symlinked subdir' '
79 git commit -m push ./file &&
83 git show HEAD:subdir/file >actual &&
84 test_cmp expect actual