diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-02-02 16:21:42 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-02-02 16:21:42 -0400 |
| commit | c7dacb9ebb1b045e4d2cc60590c6dd91bc9db929 (patch) | |
| tree | 89e03840fc5d211e7d3277eb050f26473cdf67b3 /doc/walkthrough/syncing.mdwn | |
| parent | 1400b79baf124d58374e638bb1ced595a8828ad6 (diff) | |
update docs for sync --content
Diffstat (limited to 'doc/walkthrough/syncing.mdwn')
| -rw-r--r-- | doc/walkthrough/syncing.mdwn | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/walkthrough/syncing.mdwn b/doc/walkthrough/syncing.mdwn index 0c8d52559..57fe47db0 100644 --- a/doc/walkthrough/syncing.mdwn +++ b/doc/walkthrough/syncing.mdwn @@ -15,13 +15,13 @@ Let's look at what the sync command does in more detail: push laptop ok -After you run sync, the repository will be updated with all changes made to -its remotes, and any changes in the repository will be pushed out to its -remotes, where a sync will get them. This is especially useful when using -git in a distributed fashion, without a -[[central bare repository|tips/centralized_git_repository_tutorial]]. See -[[sync]] for details. +After you run sync, the git repository will be updated with all changes +made to its remotes, and any changes in the git repository will be pushed +out to its remotes, where a sync will get them. This is especially useful +when using git in a distributed fashion, without a [[central bare +repository|tips/centralized_git_repository_tutorial]]. See [[sync]] for +details. -Note that syncing only syncs the metadata about your files that is stored -in git. It does not sync the contents of files, that are managed by -git-annex. +By default `git annex sync` only syncs the metadata about your +files that is stored in git. It does not sync the contents of files, that +are managed by git-annex. To do that, you can use `git annex sync --content` |