diff options
author | Joey Hess <joey@kitenet.net> | 2011-12-31 14:50:40 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2011-12-31 14:50:40 -0400 |
commit | f165e4aa997ecb34e2f225d405781a1789806d75 (patch) | |
tree | 4fee7a5e6e920079b2f02bb753578b25326d9ab0 /doc/walkthrough/syncing.mdwn | |
parent | dd41be54f9b338f9dce8f623db2acc96aa70439b (diff) |
add section on syncing to the walkthrough
Diffstat (limited to 'doc/walkthrough/syncing.mdwn')
-rw-r--r-- | doc/walkthrough/syncing.mdwn | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/doc/walkthrough/syncing.mdwn b/doc/walkthrough/syncing.mdwn new file mode 100644 index 000000000..38f0f8acc --- /dev/null +++ b/doc/walkthrough/syncing.mdwn @@ -0,0 +1,25 @@ +Notice that in the [[previous example|getting_file_content]], you had to +git fetch and merge from laptop first. This lets git-annex know what has +changed in laptop, and so it knows about the files present there and can +get them. + +If you have a lot of repositories to keep in sync, manually fetching and +merging from them can become tedious. To automate it there is a handy +sync command, which also even commits your changes for you. + + # cd /media/usb/annex + # git annex sync + commit + nothing to commit (working directory clean) + ok + pull laptop + ok + 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. |