summaryrefslogtreecommitdiff
path: root/doc/transferring_data.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-04 12:31:01 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-04 12:31:01 -0400
commit69c14d130bc7a754e3a4fa184ff317690ad48ca6 (patch)
treeb669edb6488ded07ab2d7e105a9f05c9d8453d53 /doc/transferring_data.mdwn
parentc5c7eaf00917d8654c82de5a4b17465b354f8fbf (diff)
update
Diffstat (limited to 'doc/transferring_data.mdwn')
-rw-r--r--doc/transferring_data.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/transferring_data.mdwn b/doc/transferring_data.mdwn
new file mode 100644
index 000000000..9526a3e48
--- /dev/null
+++ b/doc/transferring_data.mdwn
@@ -0,0 +1,14 @@
+git-annex can transfer data to or from any of a repository's git remotes.
+Depending on where the remote is, the data transfer is done using rsync
+(over ssh, with automatic resume), or plain cp (with copy-on-write
+optimisations on supported filesystems).
+
+It's equally easy to transfer a single file to or from a repository,
+or to launch a retrievel of a massive pile of files from whatever
+repositories they are scattered amoung.
+
+git-annex automatically uses whatever remotes are currently accessible,
+preferring ones that are less expensive to talk to.
+
+[[!img repomap.png caption="A real-world repository interconnection map
+(generated by git-annex map)"]]