In .gitattributes, the git-annex-numcopies attribute can be used to control the number of copies to retain of different types of files.
This commit is contained in:
parent
92e5d28ca8
commit
653ad35a9f
14 changed files with 87 additions and 75 deletions
|
@ -3,8 +3,11 @@ your git repository's `.git` directory, not in some external data store.
|
|||
|
||||
It's important that data not get lost by an ill-considered `git annex drop`
|
||||
command. So, then using those backends, git-annex can be configured to try
|
||||
to keep N copies of a file's content available across all repositories. By
|
||||
default, N is 1; it is configured by annex.numcopies.
|
||||
to keep N copies of a file's content available across all repositories.
|
||||
|
||||
By default, N is 1; it is configured by annex.numcopies. This default
|
||||
can be overridden on a per-file-type basis by the git-annex-numcopies
|
||||
setting in the `.gitattributes` file.
|
||||
|
||||
`git annex drop` attempts to check with other git remotes, to check that N
|
||||
copies of the file exist. If enough repositories cannot be verified to have
|
||||
|
|
|
@ -275,6 +275,12 @@ but the SHA1 backend for ogg files:
|
|||
* git-annex-backend=WORM
|
||||
*.ogg git-annex-backend=SHA1
|
||||
|
||||
The numcopies setting can also be configured on a per-file-type basis via
|
||||
the `git-annex-numcopies` attribute. For example, this makes two copies
|
||||
be needed for ogg files:
|
||||
|
||||
*.ogg git-annex-numcopies=2
|
||||
|
||||
# FILES
|
||||
|
||||
These files are used, in your git repository:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue