summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-08-19 12:48:39 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-08-19 12:48:39 -0400
commit0ee80746210d6d5d01bc199212da4b5d39ad14b6 (patch)
tree5f30ca30f8a0d948fa49b4a413970037bc262a34 /doc
parent10ee24d68a077d79e479a6b46947c204ef89d08f (diff)
response
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/mesh_configurations/comment_1_0712fa3d50ca6092bd7d98c945b5cc31._comment23
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/forum/mesh_configurations/comment_1_0712fa3d50ca6092bd7d98c945b5cc31._comment b/doc/forum/mesh_configurations/comment_1_0712fa3d50ca6092bd7d98c945b5cc31._comment
new file mode 100644
index 000000000..a97ade40d
--- /dev/null
+++ b/doc/forum/mesh_configurations/comment_1_0712fa3d50ca6092bd7d98c945b5cc31._comment
@@ -0,0 +1,23 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-08-19T16:40:16Z"
+ content="""
+It's easy to see why a file is not copied from source repo A to source repo
+B: The preferred content expression for a source repo is "not (copies=1)",
+so a source repo will not want to get any files from any other repo.
+
+You probably want to make the central repo use transfer; that's basically
+what it's for. Note that a transfer repo hangs onto file content until it
+reaches all client repos. So you might want to change the preferred content
+expression to refer to backup repos. Something as simple as this might
+work:
+
+ not inallgroup=backup
+
+I don't see any reason why a file wouldn't move from B to backup repo C,
+but I don't see anything in your transcript that shows that not happening
+either. Your transcript doesn't actually show running any git-annex commands
+that move file contents at all; no git annex copy/move, and the sync is not
+run with --content...
+"""]]