From 4b6cb2b917b69fc2a06e0a28b9cfa18c47fcf97f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 4 Jun 2021 14:00:58 -0400 Subject: [PATCH] comment --- ..._3_f56ac8a714facc8aafb60d3da815021b._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/forum/distributed_borg/comment_3_f56ac8a714facc8aafb60d3da815021b._comment diff --git a/doc/forum/distributed_borg/comment_3_f56ac8a714facc8aafb60d3da815021b._comment b/doc/forum/distributed_borg/comment_3_f56ac8a714facc8aafb60d3da815021b._comment new file mode 100644 index 0000000000..c150843763 --- /dev/null +++ b/doc/forum/distributed_borg/comment_3_f56ac8a714facc8aafb60d3da815021b._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2021-06-04T17:53:51Z" + content=""" +Yeah, that's the pattern for any special remote: Initialize once and +enableremote everywhere else. Otherwise you have a bunch of different +special remotes that happened to be initialized more or less the same +but git-annex doesn't know you consider them all to be the same place. + +I'd be keen to improve whatever docs might have led to the multiple +initremote mistake. The man page for initremote does +say to use enableremote in other clones. But maybe you were +following a page like +[[tips/using_borg_for_efficient_storage_of_old_annexed_files]] and just +assumed you'd follow that same procedure in each clone? +"""]]