summaryrefslogtreecommitdiff
path: root/doc/sync.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-02-02 16:21:42 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-02-02 16:21:42 -0400
commitc7dacb9ebb1b045e4d2cc60590c6dd91bc9db929 (patch)
tree89e03840fc5d211e7d3277eb050f26473cdf67b3 /doc/sync.mdwn
parent1400b79baf124d58374e638bb1ced595a8828ad6 (diff)
update docs for sync --content
Diffstat (limited to 'doc/sync.mdwn')
-rw-r--r--doc/sync.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/sync.mdwn b/doc/sync.mdwn
index 37b2b1b45..0250d2fef 100644
--- a/doc/sync.mdwn
+++ b/doc/sync.mdwn
@@ -36,3 +36,9 @@ The workflow for using `git annex sync` is simple:
* Run `git annex sync` to save the changes.
* Next time you're working on a different clone of that repository,
run `git annex sync` to update it.
+
+Note that by default, `git annex sync` only synchronises the git
+repositories, but does not transfer the content of annexed files. If you
+want to fully synchronise two repositories content,
+you can use `git annex sync --content`. You can also configure
+[[preferred_content]] settings to make only some content be synced.