mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

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

Browse source
This commit is contained in:
Joey Hess 2013-01-06 14:37:14 -04:00
parent 909f67443f
commit 2cdb7326b9
1 changed files with 0 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/preferred_content.mdwn
View file

@ -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