From adfe5a4a4c0e92f34408af01b0e87944d8cc10f6 Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Fri, 17 Nov 2023 08:45:56 +0000 Subject: [PATCH] Added a comment --- .../comment_7_3e66ef8493d2839cb26418788c510463._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/very_slow_on_exfat_drives/comment_7_3e66ef8493d2839cb26418788c510463._comment diff --git a/doc/forum/very_slow_on_exfat_drives/comment_7_3e66ef8493d2839cb26418788c510463._comment b/doc/forum/very_slow_on_exfat_drives/comment_7_3e66ef8493d2839cb26418788c510463._comment new file mode 100644 index 0000000000..d8f8111ed4 --- /dev/null +++ b/doc/forum/very_slow_on_exfat_drives/comment_7_3e66ef8493d2839cb26418788c510463._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="comment 7" + date="2023-11-17T08:45:56Z" + content=""" +I'm not sure exactly what you mean. If you `git annex move`d a file from a local repo to the bare repo on the HDD, your local repo should know about this immediately. I'm not sure if an immediate `git annex move` *on the HDD* afterwards knows about this. Sounds like it should but maybe it doesn't for performance reasons. That would explain the need for a subsequent `sync`. In general, I would recommend setting up preferred content expressions for each repo, and then always just run `git annex assist` to have it sync everything. Slower than manual moving and copying though, but less worrying. +"""]]