diff options
author | 2015-09-21 15:27:36 -0400 | |
---|---|---|
committer | 2015-09-21 15:27:36 -0400 | |
commit | b6cb6199f2ef7062cfe8ca5017bd04cba1b053ef (patch) | |
tree | 67e9af268392e9e244f01dc0796c7398b56715dd /doc | |
parent | c4a950f9144514b21088ef2963978b0c84701b1f (diff) |
followup more
Diffstat (limited to 'doc')
2 files changed, 19 insertions, 1 deletions
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 95dbe803f..f06ebdaa7 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 000000000..d21e584a6 --- /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. +"""]] |