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

fix outdated docs

Browse source 
When a repo is in multiple standard groups,
Logs.PreferredContent.makeMatcher uses unknownMatcher,
so will not get everything, but instead defaults to wanting whatever is
present.
This commit is contained in:
Joey Hess 2018-01-15 14:25:35 -04:00
parent cce2d416d6
commit 37d7a1b768
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 0 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/git-annex-preferred-content.mdwn
View file

@ -164,8 +164,6 @@ elsewhere to allow removing it).
When a repository is in exactly one such group, you can use the "standard" When a repository is in exactly one such group, you can use the "standard"
keyword in its preferred content expression, to match whatever content keyword in its preferred content expression, to match whatever content
the group's expression matches. the group's expression matches.
(If a repository is put into multiple standard
groups, "standard" will match anything.. so don't do that!)
Most often, the whole preferred content expression is simply "standard". Most often, the whole preferred content expression is simply "standard".
But, you can do more complicated things, for example: But, you can do more complicated things, for example: