From c25ade4d970e5421ccb929971911ad7ed90c8721 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 19 Aug 2022 20:19:50 +0000 Subject: [PATCH] Added a comment: imports and symlinks --- ...t_7_4f9816f7c9a61289bef98820b1ec25cc._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/git-annex-import_imports_outside_of_directory/comment_7_4f9816f7c9a61289bef98820b1ec25cc._comment diff --git a/doc/bugs/git-annex-import_imports_outside_of_directory/comment_7_4f9816f7c9a61289bef98820b1ec25cc._comment b/doc/bugs/git-annex-import_imports_outside_of_directory/comment_7_4f9816f7c9a61289bef98820b1ec25cc._comment new file mode 100644 index 0000000000..0bc559ab0c --- /dev/null +++ b/doc/bugs/git-annex-import_imports_outside_of_directory/comment_7_4f9816f7c9a61289bef98820b1ec25cc._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="imports and symlinks" + date="2022-08-19T20:19:50Z" + content=""" +Re: new manpage description that says + +>symbolic links in the directory being imported are skipped to avoid +>accidentially importing things outside the directory that import was ran +>on + +In my use cases, skipping symlinks (instead of importing them as git symlinks) would make the imported tree unusable by tools that expect specific filenames in specific subdirs of the tree, +when these filenames were symlinks in the original tree. +Could the symlinks be imported as standard git symlinks instead of skipping them? Worst case, a checkout of the repo will have symlinks to non-existing targets -- this can be fixed by mounting volumes with the right paths. OTOH, having filenames missing from the imported tree because they happened to be symlinks in the original tree can cause all sorts of errors. Import is much simpler to think about if it's guaranteed to replicate the full original tree structure, like `tar` does. +"""]]