summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-09-13 14:34:55 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-09-13 14:34:55 -0400
commitd8f1761b54ef430560d7e8debf10e7310dfd158b (patch)
tree5d0c1bab91c69a20053a92a988eda0b96e42adf8 /doc
parent485c4a6b1b74e96292cb6434a8bc4319417753e3 (diff)
format; close
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn2
-rw-r--r--doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment6
2 files changed, 5 insertions, 3 deletions
diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn
index f3bff8683..c5a75b361 100644
--- a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn
+++ b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn
@@ -20,3 +20,5 @@ A is running Debian testing with git-annex 4.20130827, B and S are running Debia
I tried this setup before with direct mode and different preferred content settings (A, B as client, S as backup or archive), and syncing of git and file data was working then.
Despite being able to run 'sync' it is at least inconvenient to not have automatically updated file location information when I run the assistant. (I could then just run without it, but I had it happen to me that I setup a local repo w/o assistant, and when I ran assistant, expecting it would tell me "there are no local repos, would you like to create one?" it somehow automatically found the manually created one and started copying files. But that's another problem.)
+
+> [[done]] unless my diagnosis is wrong. --[[Joey]]
diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment
index bc2a92a00..05a3d7f74 100644
--- a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment
+++ b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment
@@ -6,7 +6,7 @@
content="""
You have described the following git-annex network:
- A --(ssh)-- S --(ssh)-- B
+ A --(ssh)-- S --(ssh)-- B
So A automatically syncs to S. But there is no way at all for A to tell B that it has made changes. So B does not automatically sync.
@@ -16,8 +16,8 @@ The git-annex webapp will detect this kind of situation, and display this alert:
Once you set up an XMPP account, the network will look like:
- A --(ssh)-- S --(ssh)-- B
- \_________(XMPP)_______/
+ A --(ssh)-- S --(ssh)-- B
+ \_________(XMPP)_______/
And now B will immediatly know when A has pushed a change to S, and will go get it.