document -C behavior with exporttree remotes

doc/bugs/sync_-C_can_export_other_files.mdwn

@@ -12,3 +12,6 @@ not send it to any other remotes, since it's not in directory foo.
 
 Also this affects `git-annex satisfy`, and other related commands too.
 --[[Joey]]
+
+> Decided to just document this behavior since there does not seem to be
+> any good alternative behavior. [[done]] --[[Joey]]

doc/git-annex-push.mdwn

@@ -28,7 +28,8 @@ only local `master` to remote `master`, but also to remote `synced/master`
 sync`) is later run on the remote, it will merge the `synced/` branches
 that were pushed to it.
 
-Some special remotes allow exporting a tree of files to them,
+Some special remotes allow exporting a tree of files to them
+(`exporttree=yes`),
 and this command can be used to push to those remotes as well
 as regular git remotes. See [[git-annex-export]](1) for details
 about how those special remotes work. In order for this command to export
@@ -91,6 +92,9 @@ See [[git-annex-preferred-content]](1).
 
   This option can be repeated multiple times with different paths.
 
+  Note that this option is ignored when syncing with "exporttree=yes"
+  remotes.
+
 * `--all` `-A`
 
   Usually this command operates on annexed files in the current branch.

doc/git-annex-satisfy.mdwn

@@ -32,6 +32,9 @@ imported to or exported from special remotes.
 
   This option can be repeated multiple times with different paths.
 
+  Note that this option is ignored when syncing with "exporttree=yes"
+  remotes.
+
 * `--jobs=N` `-JN`
 
   Enables parallel processing with up to the specified number of jobs

doc/git-annex-sync.mdwn

@@ -38,6 +38,9 @@ when syncing with repositories that have preferred content configured.
 
   This option can be repeated multiple times with different paths.
 
+  Note that this option does not prevent exporting other files to an 
+  "exporttree=yes" remote.
+
 * `--commit`, `--no-commit`
 
   A commit is done by default (unless `annex.autocommit` is set to false).