aboutsummaryrefslogtreecommitdiff
path: root/doc/preferred_content.mdwn
Commit message (Collapse)AuthorAge
* remove a paragraph about in=, which is not available in preferred content ↵Gravatar Joey Hess2013-01-06
| | | | expressions
* fix preferred content definition for the backup groupGravatar Joey Hess2012-12-10
| | | | | Broken by commit 2a04e215e10469ee3bab5d1a5d6d76b0c35cc46c, which made empty preferred content strings match nothing, rather than everything.
* webapp and assistant glacier supportGravatar Joey Hess2012-11-24
|
* Replace "in=" with "present" in preferred content expressionsGravatar Joey Hess2012-10-19
| | | | | | | | | | | | in= was problimatic in two ways. First, it referred to a remote by name, but preferred content expressions can be evaluated elsewhere, where that remote doesn't exist, or a different remote has the same name. This name lookup code could error out at runtime. Secondly, in= seemed pretty useless. in=here did not cause content to be gotten, but it did let present content be dropped. present is more useful, although "not present" is unstable and should be avoided.
* logic errorGravatar Joey Hess2012-10-14
|
* handle transfer repository bootstrappingGravatar Joey Hess2012-10-14
| | | | | | | | When there's just 1 client repo, and a transfer repo is created, its preferred content will now make it prefer all content in the client, even though there's no other client yet to transfer it to. Presumably, another client will be created eventually. It might even already exist, and the transfer repo will be used to connect up with it.
* standard preferred content settings for client, transfer, backup, and ↵Gravatar Joey Hess2012-10-10
| | | | | | | | archive repositories I've designed these to work well together, I hope. If I get it wrong, I can just change the code in one place, since these expressions won't be stored in the git-annex branch.
* wired preferred content up to get, copy, and drop --autoGravatar Joey Hess2012-10-08