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

Improve behavior when unable to parse a preferred content expression (thanks, ion).

Browse source 
Fall back to "present" as the preferred conent expression, which will
not result in any content movement.
This commit is contained in:
Joey Hess 2014-03-20 00:10:12 -04:00
parent 9aa31b71f3
commit ed30b81e2c
4 changed files with 38 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/preferred_content.mdwn
View file

@ -149,9 +149,13 @@ group and make its preferred content be "groupwanted" will use it.
It's important that all clones of a repository can understand one-another's
preferred content expressions, especially when using the git-annex
assistant. So using newly added keywords can cause a problem if
an older version of git-annex is in use elsewhere. When an old version
of git-annex sees a keyword it does not understand, it assumes that keyword
will match *all* files.
an older version of git-annex is in use elsewhere.
Before git-annex version 5.20140320, when git-annex saw a keyword it
did not understand, it defaulted to assuming *all* files were
preferred content. From version 5.20140320, git-annex has a nicer fallback
behavior: When it is unable to parse a preferred content expression,
it assumes all files that are currently present are preferred content.
Here are recent changes to preferred content expressions, and the version
they were added in.