Clemens Buchacher <drizzd@xxxxxx> writes: > I didn't write the test, but to me it looks like the test wants to > make sure that while the symlink is removed, the tree it's pointing > to is not removed. Yes, I agree with that reading. I'd squash in this on top, first making sure that "do not overwrite untracked symlinks" (which is the title of this patch) won't be broken, and then the original test that wanted to make sure that checking out a/b/c/d when a/b is pointing to an unrelated part of the tree does not nuke whatever is pointed at that symbolic link. Thanks. My unhappiness with the undescriptive "check_leading_path()" still remains, though... diff --git a/t/t6035-merge-dir-to-symlink.sh b/t/t6035-merge-dir-to-symlink.sh index 1de285b..2599ae5 100755 --- a/t/t6035-merge-dir-to-symlink.sh +++ b/t/t6035-merge-dir-to-symlink.sh @@ -17,13 +17,21 @@ test_expect_success SYMLINKS 'create a commit where dir a/b changed to symlink' git commit -m "dir to symlink" ' -test_expect_success SYMLINKS 'keep a/b-2/c/d across checkout' ' +test_expect_success SYMLINKS 'checkout does not clobber untracked symlink' ' git checkout HEAD^0 && git reset --hard master && git rm --cached a/b && git commit -m "untracked symlink remains" && - git checkout -f start^0 && - test -f a/b-2/c/d + test_must_fail git checkout start^0 +' + +test_expect_success SYMLINKS 'a/b-2/c/d is kept when clobbering symlink b' ' + git checkout HEAD^0 && + git reset --hard master && + git rm --cached a/b && + git commit -m "untracked symlink remains" && + git checkout -f start^0 && + test -f a/b-2/c/d ' test_expect_success SYMLINKS 'checkout should not have deleted a/b-2/c/d' ' -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html