remove a paragraph about in=, which is not available in preferred content expressions

1 files changed, 0 insertions, 9 deletions

diff --git a/doc/preferred_content.mdwn b/doc/preferred_content.mdwn
index 6408656e4..6538bcc80 100644
--- a/doc/preferred_content.mdwn
+++ b/doc/preferred_content.mdwn
@@ -58,15 +58,6 @@ content be dropped only when there are currently 3 copies of it, including
 the repo it's being dropped from. This is different than running `git annex
 drop --copies=2`, which will drop files that current have 2 copies.
 
-A wrinkle of this approach is how `in=` is handled. When deciding if
-content should be dropped, git-annex looks at the current status, not
-the status if the content would be dropped. So `in=here` means that
-any currently present content is preferred, which can be useful if you
-want manual control over content. Meanwhile `not (in=here)` should be
-avoided -- it will cause content that's not here to be preferred,
-but once the content arrives, it'll stop being preferred and will be
-dropped again!
-
 ## difference: "present"
 
 There's a special "present" keyword you can use in a preferred content