From 066c4f1efc180499636f488abd97fe8f7c2c7255 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Wed, 14 Apr 2021 18:04:53 +0000 Subject: [PATCH] Added a comment: comment to joey response on cp --reflink workaround --- ...comment_3_20e31ffc7c490215db7a3f1a0a3b813c._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/todo/import_from_directory_does_not_use_cp_--reflink__63___/comment_3_20e31ffc7c490215db7a3f1a0a3b813c._comment diff --git a/doc/todo/import_from_directory_does_not_use_cp_--reflink__63___/comment_3_20e31ffc7c490215db7a3f1a0a3b813c._comment b/doc/todo/import_from_directory_does_not_use_cp_--reflink__63___/comment_3_20e31ffc7c490215db7a3f1a0a3b813c._comment new file mode 100644 index 0000000000..db6a3d6999 --- /dev/null +++ b/doc/todo/import_from_directory_does_not_use_cp_--reflink__63___/comment_3_20e31ffc7c490215db7a3f1a0a3b813c._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment to joey response on cp --reflink workaround" + date="2021-04-14T18:04:49Z" + content=""" +> Of course, if you can get the content into the git-annex repository by other means like manual cp --reflink, git-annex will never have any reason to transfer the imported file from the remote, so that workaround would work. + +FWIW: doing that now. Minor pain will come later when I will need to update it (only once again) with a new sync'ed data (some files will be added, some removed) -- to simplify my own life I will just `rm -rf` in target git-annex repo, redo `cp --reflink` and redo `datalad save` (which will take care about removing gone, and `git-annex add` on all others -- but that would take again many hours to complete even though only a handful of files will be changed) +"""]] -- 2.30.2