aboutsummaryrefslogtreecommitdiff
path: root/doc/preferred_content.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-01-16 13:47:07 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-01-16 13:47:07 -0400
commitf2fc88bb1aeceab159cdba73dfa0bbb737f30c4a (patch)
treebdd5843901cdbd5856ae594ea1f5e1a6f321248a /doc/preferred_content.mdwn
parent693d324e2b3e7af786a17f251fa8075593064883 (diff)
document "unused" in preferred content expressions
Diffstat (limited to 'doc/preferred_content.mdwn')
-rw-r--r--doc/preferred_content.mdwn21
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/preferred_content.mdwn b/doc/preferred_content.mdwn
index ec499de25..b81c45fbf 100644
--- a/doc/preferred_content.mdwn
+++ b/doc/preferred_content.mdwn
@@ -154,6 +154,27 @@ becomes
metadata=tag=done
+### difference: unused
+
+The --unused option makes git-annex operate on every key that `git annex
+unused` has determined to be unused. The corresponding `unused` keyword
+in a preferred content expression also matches those keys.
+
+However, the latter doesn't make git-annex consider those keys. So
+when git-annex is only checking preferred content expressions against files
+in the repository (which are obviously used), `unused` in a preferred
+content expression won't match anything.
+
+So when is `unused` useful in a preferred content expression?
+
+Using `git annex sync --content --all` will ensure that all keys, including
+unused ones, are examined and the preferred content expressions followed.
+
+The git-annex assistant periodically scans for unused files, and
+moves them to some repository whose preferred content expression
+matches "unused". (Or, if annex.expireunused is set, it may just delete
+them.)
+
## upgrades
It's important that all clones of a repository can understand one-another's