From 144500f19d85c568910d722cc056ee7ca8f54fdb Mon Sep 17 00:00:00 2001 From: imlew Date: Fri, 17 Nov 2023 08:23:32 +0000 Subject: [PATCH] Added a comment: one more question --- ...mment_6_a6c5e8dc86ed6b4b5ff45f66f5bad50a._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/very_slow_on_exfat_drives/comment_6_a6c5e8dc86ed6b4b5ff45f66f5bad50a._comment diff --git a/doc/forum/very_slow_on_exfat_drives/comment_6_a6c5e8dc86ed6b4b5ff45f66f5bad50a._comment b/doc/forum/very_slow_on_exfat_drives/comment_6_a6c5e8dc86ed6b4b5ff45f66f5bad50a._comment new file mode 100644 index 0000000000..4bb4cb5291 --- /dev/null +++ b/doc/forum/very_slow_on_exfat_drives/comment_6_a6c5e8dc86ed6b4b5ff45f66f5bad50a._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="imlew" + avatar="http://cdn.libravatar.org/avatar/23858c3eed3c3ea9e21522f4c999f1ed" + subject="one more question" + date="2023-11-17T08:23:32Z" + content=""" +I'm not sure if this is caused by the disk's repo being bare, but after I have `git annex move`d a file there I still need to run `git annex sync` in the local source repo before I can find or copy the file to a third repo (in this case a second repo on my laptop). + +This is a little confusing because it seems the bare repo on the disk doesn't know it has the files that have been moved to it. + +Is this because it is bare, am I doing something wrong or why doesn't `git annex move` result in the target knowing that it has a given file? +"""]] -- 2.30.2