Adding a use case from joeyh's comment http://git-annex.branchable.com/special_remotes/rsync/#comment-910be826fc1e7a3c01840d4063059907

1 files changed, 9 insertions, 1 deletions

diff --git a/doc/special_remotes.mdwn b/doc/special_remotes.mdwn
index 978989503..a0102fcaa 100644
--- a/doc/special_remotes.mdwn
+++ b/doc/special_remotes.mdwn
@@ -18,7 +18,15 @@ They cannot be used by other git commands though.
 * [[hook]]
 
 The above special remotes can be used to tie git-annex 
-into many cloud services. Here are specific instructions
+into many cloud services. 
+
+There are many use cases for a special remote. You could use it as a backup. You could use it to archive files offline in a drive with encryption enabled so if the drive is stolen your data is not. You could git annex move --to specialremote large files when your local drive is getting full, and then git annex move the files back when free space is again available. You could have one repository copy files to a special remote, and then git annex get them on another repository, to transfer the files between computers that do not communicate directly. 
+
+The git-annex assistant makes it easy to set up rsync remotes using this last scenario, which is referred to as a transfer repository, and arranges to drop files from the transfer repository once they have been transferred to all known clients.
+
+None of these use cases are particular to particular special remote types. Most special remotes can all be used in these and other ways. It largely doesn't matter for your use what underlying transport the special remote uses.
+
+Here are specific instructions
 for various cloud things:
 
 * [[Amazon_S3|tips/using_Amazon_S3]]