summaryrefslogtreecommitdiff
path: root/doc/preferred_content.mdwn
Commit message (Collapse)AuthorAge
* add --want-get and --want-drop optionsGravatar Joey Hess2013-10-28
| | | | | New --want-get and --want-drop options which can be used to test preferred content settings. For example, "git annex find --in . --want-drop"
* The "git annex content" command is renamed to "git annex wanted".Gravatar Joey Hess2013-10-28
|
* update to use enableremote for changing preferreddir settingsGravatar Joey Hess2013-07-16
|
* content: New command line way to view and configure a repository's preferred ↵Gravatar Joey Hess2013-05-25
| | | | content settings.
* per-IA-item content directoriesGravatar Joey Hess2013-04-25
|
* Automatically register public urls for files uploaded to the Internet Archive.Gravatar Joey Hess2013-04-25
|
* Internet Archive!Gravatar Joey Hess2013-04-25
| | | | | | | * Add public repository group. * webapp: Can now set up Internet Archive repositories. TODO: Enabling IA repositories.
* better archive directory handlingGravatar Joey Hess2013-04-06
| | | | | Adjust preferred content expressions so that content in archive directories is preferred until it has reached an archive or smallarchive repository.
* fix preferred content check for 1 semitrusted or better copyGravatar Joey Hess2013-04-02
| | | | | | | | | Let's make semitrusted+:1 mean that, since it cannot be expressed easily with the current syntax (could use (semitrusted:1 or trusted:1), but that does not scale to higher values than 2 copy, and also fails if I add more trust levels). Thanks to Andy for spotting this bug by just reading my blog.
* Adjust built-in preferred content expressions to make most types of ↵Gravatar Joey Hess2013-03-31
| | | | repositories want content that is only located on untrusted or dead repositories.
* Add incrementalbackup repository group.Gravatar Joey Hess2013-03-16
|
* fix headerGravatar Joey Hess2013-02-24
|
* adjust archive exclusionGravatar Joey Hess2013-01-22
|
* manual and source repository groupsGravatar Joey Hess2013-01-21
|
* 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