From 02fab1ca2a3b3cd035d57830842a9237c2a5b4cd Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Thu, 6 Jul 2023 05:52:50 +0000 Subject: [PATCH] Added a comment --- ...comment_8_c666e3ef20e823230392a70d6b588e7d._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/todo/new_command_for_syncing_content_only/comment_8_c666e3ef20e823230392a70d6b588e7d._comment diff --git a/doc/todo/new_command_for_syncing_content_only/comment_8_c666e3ef20e823230392a70d6b588e7d._comment b/doc/todo/new_command_for_syncing_content_only/comment_8_c666e3ef20e823230392a70d6b588e7d._comment new file mode 100644 index 0000000000..b2fd3654f6 --- /dev/null +++ b/doc/todo/new_command_for_syncing_content_only/comment_8_c666e3ef20e823230392a70d6b588e7d._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="comment 8" + date="2023-07-06T05:52:50Z" + content=""" +Aah okay, I forgot there's `lackingcopies`. So if one adds `or lackingcopies=1` to every (sensible) remote's preferred content, then git annex is allowed to put \"fragile\" files there which haven't been copied enough yet (until there eventually are and they're removed again). I was missing that link, now everything makes sense. + +And now I see that this is exactly what the `client` group does 😅 +"""]] -- 2.30.2