e213ef310f
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
17 lines
891 B
Markdown
17 lines
891 B
Markdown
Required content settings can be configured to do more complicated
|
|
things than just setting the required number of [[copies]] of your data.
|
|
For example, you could require that data be archived in at least two
|
|
archival repositories, and also require that one copy be stored offsite.
|
|
|
|
The format of required content expressions is the same as
|
|
[[preferred_content]] expressions.
|
|
|
|
Required content settings can be edited using `git annex vicfg`.
|
|
Each repository can have its own settings, and other repositories will
|
|
try to honor those settings when interacting with it.
|
|
|
|
While [[preferred_content]] expresses a preference, it can be overridden
|
|
by simply using `git annex drop`. On the other hand, required content
|
|
settings are enforced; `git annex drop` will refuse to drop a file if
|
|
doing so would violate its required content settings.
|
|
(Although even this can be overridden using `--force`).
|