diff --git a/doc/bugs/sync-git-annex_branch_not_syncing_in_the_assistant/comment_1_b832288844a3e7e944fa08a6edb97d29._comment b/doc/bugs/sync-git-annex_branch_not_syncing_in_the_assistant/comment_1_b832288844a3e7e944fa08a6edb97d29._comment
index 95dbe803fe..f06ebdaa77 100644
--- a/doc/bugs/sync-git-annex_branch_not_syncing_in_the_assistant/comment_1_b832288844a3e7e944fa08a6edb97d29._comment
+++ b/doc/bugs/sync-git-annex_branch_not_syncing_in_the_assistant/comment_1_b832288844a3e7e944fa08a6edb97d29._comment
@@ -7,7 +7,7 @@ The assistant merges the synced/git-annex branch whenever it detects (via
 inotify) that a change has been made to that git ref. 
 
 I can't reproduce a problem from the information you've given. With
-foo -- bar -- quux, and assistants running on foo and quux, any file
+`foo -> bar <- quux`, and assistants running on foo and quux, any file
 written to foo more or less immediately syncs to quux, and the git-annex
 branch is merged.
 
diff --git a/doc/bugs/sync-git-annex_branch_not_syncing_in_the_assistant/comment_2_fbfc8929497f609916d9f3e5a0a9b531._comment b/doc/bugs/sync-git-annex_branch_not_syncing_in_the_assistant/comment_2_fbfc8929497f609916d9f3e5a0a9b531._comment
new file mode 100644
index 0000000000..d21e584a69
--- /dev/null
+++ b/doc/bugs/sync-git-annex_branch_not_syncing_in_the_assistant/comment_2_fbfc8929497f609916d9f3e5a0a9b531._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2015-09-21T19:21:30Z"
+ content="""
+Note that I'm assuming that bar is a remote of both foo and of quux.
+That seems like a reasonable reading of what you described, and is a
+reasonable configuration, but perhaps you were trying to describe some
+other configuration. 
+
+In [[forum/mesh_configurations]] you seem to instead
+describe a chain of remotes, where bar is a remote of foo, and quux is a
+remote of bar: `foo -> bar -> quux`. In this configuration, running the assistant on 
+foo and quux, but not on bar, would not result in changes made on quux
+ever getting to foo, because quux has no way to push objects to bar. So, I
+don't think that's the configuration you meant either. But lack of clarity
+in bug report makes it hard to know.
+"""]]