diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-06-22 15:47:02 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-06-22 15:47:02 -0400 |
| commit | 153942cc6eb4e1ab5ae730261aa3266fd1b41721 (patch) | |
| tree | ec942ce2b78a595dd142f6460cb2fbb0fbc7cd2c | |
| parent | cf9bf920e8052edbcee9dd31bfb1c9b421296d14 (diff) | |
update
| -rw-r--r-- | doc/design/assistant/syncing.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/design/assistant/syncing.mdwn b/doc/design/assistant/syncing.mdwn index 56c9692e3..05c7483dd 100644 --- a/doc/design/assistant/syncing.mdwn +++ b/doc/design/assistant/syncing.mdwn @@ -5,7 +5,7 @@ all the other git clones, at both the git level and the key/value level. 1. Can use `git annex sync`, which already handles bidirectional syncing. When a change is committed, launch the part of `git annex sync` that pushes - out changes. + out changes. **done**; changes are pushed out to all remotes in parallel 1. Watch `.git/refs/remotes/` for changes (which would be pushed in from another node via `git annex sync`), and run the part of `git annex sync` that merges in received changes, and follow it by the part that pushes out |