From df65c4796ded25ac2bc8c5745c7db570b8195f8f Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Thu, 2 Jul 2020 20:22:26 +0000 Subject: [PATCH] Added a comment --- .../comment_4_30a3ebad1c2a0129b7629842edc9095f._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/importing_from_special_remote_without_downloading/comment_4_30a3ebad1c2a0129b7629842edc9095f._comment diff --git a/doc/todo/importing_from_special_remote_without_downloading/comment_4_30a3ebad1c2a0129b7629842edc9095f._comment b/doc/todo/importing_from_special_remote_without_downloading/comment_4_30a3ebad1c2a0129b7629842edc9095f._comment new file mode 100644 index 0000000000..a422d62b0a --- /dev/null +++ b/doc/todo/importing_from_special_remote_without_downloading/comment_4_30a3ebad1c2a0129b7629842edc9095f._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 4" + date="2020-07-02T20:22:25Z" + content=""" +Thanks -- this would solve (among other things) [[bugs/removeLink_failed_when_initializing_a_repo_in_a_VirtualBox_shared_folder]]: I could put the git-annex repo on the normal filesystem inside the VM, and only the directory special remote would then deal with the broken vboxsf filesystem. import-tree *with* copying isn't possible as the files are too big. +"""]]