3 files changed, 14 insertions, 1 deletions
diff --git a/doc/git-annex-export.mdwn b/doc/git-annex-export.mdwn
index a8f9f5cb3..1d7170cee 100644
--- a/doc/git-annex-export.mdwn
+++ b/doc/git-annex-export.mdwn
@@ -29,7 +29,7 @@ Repeated exports are done efficiently, by diffing the old and new tree,
 and transferring only the changed files, and renaming files as necessary.
 
 Exports can be interrupted and resumed. However, partially uploaded files
-will be re-started from the beginning.
+will be re-started from the beginning in most cases.
 
 Once content has been exported to a remote, commands like `git annex get`
 can download content from there the same as from other remotes. However,
diff --git a/doc/special_remotes/rsync.mdwn b/doc/special_remotes/rsync.mdwn
index 2271cbc2a..7d30b4092 100644
--- a/doc/special_remotes/rsync.mdwn
+++ b/doc/special_remotes/rsync.mdwn
@@ -22,6 +22,10 @@ These parameters can be passed to `git annex initremote` to configure rsync:
 
 * `keyid` - Specifies the gpg key to use for [[encryption]].
 
+* `exporttree` - Set to "yes" to make this special remote usable
+  by [[git-annex-export]]. It will not be usable as a general-purpose
+  special remote.
+
 * `shellescape` - Optional. Set to "no" to avoid shell escaping normally
   done when using rsync over ssh. That escaping is needed with typical
   setups, but not with some hosting providers that do not expose rsynced
diff --git a/doc/todo/export/comment_8_3b93389a1f50aad0f759d361f06200e9._comment b/doc/todo/export/comment_8_3b93389a1f50aad0f759d361f06200e9._comment
new file mode 100644
index 000000000..c68f7161a
--- /dev/null
+++ b/doc/todo/export/comment_8_3b93389a1f50aad0f759d361f06200e9._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 8"""
+ date="2018-02-28T15:54:06Z"
+ content="""
+Remotes need to have a nontrivial amount of code added to them in order to
+support export. That had not been done for rsync yet. I've implemented it
+now.
+"""]]