From 39763ddee79c7af353cb868fa5ec2aee2e6252f5 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 19 Aug 2022 17:18:37 +0000 Subject: [PATCH] Added a comment: git-annex-import and symlinks --- ...omment_6_d6aaa0519faa596fa42d22fba405cbff._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/git-annex-import_imports_outside_of_directory/comment_6_d6aaa0519faa596fa42d22fba405cbff._comment diff --git a/doc/bugs/git-annex-import_imports_outside_of_directory/comment_6_d6aaa0519faa596fa42d22fba405cbff._comment b/doc/bugs/git-annex-import_imports_outside_of_directory/comment_6_d6aaa0519faa596fa42d22fba405cbff._comment new file mode 100644 index 0000000000..a35b735fdb --- /dev/null +++ b/doc/bugs/git-annex-import_imports_outside_of_directory/comment_6_d6aaa0519faa596fa42d22fba405cbff._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="git-annex-import and symlinks" + date="2022-08-19T17:18:37Z" + content=""" +>git-annex import and the directory special remote should skip over symlinks + +It should still import them as symlinks into git, just not change them to annexed files. If these are relative symlinks pointing within the tree being imported, they'll still work in the repo. If these are absolute symlinks to common files mounted on a filesystem shared by all users of the repo, you still want them in the imported repo as absolute symlinks. Absolute symlinks that happen to point within the tree being imported should be imported as annexed files. + +"""]]