Added a comment
authorimlew <imlew@web>
Thu, 18 Jan 2024 23:09:21 +0000 (23:09 +0000)
committeradmin <admin@branchable.com>
Thu, 18 Jan 2024 23:09:21 +0000 (23:09 +0000)
doc/forum/sync_content_through_repo_that_wants_nothing/comment_2_ef89154903395025bb0a0408e1c23bdf._comment [new file with mode: 0644]

diff --git a/doc/forum/sync_content_through_repo_that_wants_nothing/comment_2_ef89154903395025bb0a0408e1c23bdf._comment b/doc/forum/sync_content_through_repo_that_wants_nothing/comment_2_ef89154903395025bb0a0408e1c23bdf._comment
new file mode 100644 (file)
index 0000000..e81f301
--- /dev/null
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="imlew"
+ avatar="http://cdn.libravatar.org/avatar/23858c3eed3c3ea9e21522f4c999f1ed"
+ subject="comment 2"
+ date="2024-01-18T23:09:21Z"
+ content="""
+Using the standard transfer group wouldn't work in this situation because the remotes cannot be clients (among other reason because the server repo is bigger than the external drives).
+
+But from your answer I surmise that the local repo must want the files unless they are on the drives and no longer want them once they are on drives, is that correct?
+
+I will try letting it run overnight with the local repo's wanted being `\"not copies=2\"`. Hopefully sync will drop the local copy as soon as it has been transferred to the drive and not keep that for last.
+
+"""]]