From 0cb925525552f27ef69fbacece28beb744aa1a07 Mon Sep 17 00:00:00 2001 From: konubinix Date: Fri, 9 Aug 2013 06:22:33 +0000 Subject: [PATCH] precision about an attempt of workaround --- ...symlink_are_wrong_when_submodule_is_not_in_the_same_path.mdwn | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path.mdwn b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path.mdwn index 7c63c68ad3..3f58bd8896 100644 --- a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path.mdwn +++ b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path.mdwn @@ -47,6 +47,7 @@ This returns test -> ../.git/modules/module/annex/objects/w8/pv/SHA256E-s5--f2ca Actually, the file committed is correct. But the fact it points to '../.git/modules/module/...' makes the link work only if the repository is also a submodule and if this submodule is also located in the modules folder in the parent git repository. +I tried playing with making the repository direct and then indirect, hoping that would fix the symlinks, but it did not work. ### What version of git-annex are you using? On what operating system? $ git-annex version