Added a comment
authornobodyinperson <nobodyinperson@web>
Thu, 6 Jul 2023 05:52:50 +0000 (05:52 +0000)
committeradmin <admin@branchable.com>
Thu, 6 Jul 2023 05:52:50 +0000 (05:52 +0000)
doc/todo/new_command_for_syncing_content_only/comment_8_c666e3ef20e823230392a70d6b588e7d._comment [new file with mode: 0644]

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 (file)
index 0000000..b2fd365
--- /dev/null
@@ -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 ðŸ˜…
+"""]]