cc89699457
This is conceptually very simple, just making a 1 that was hard coded be exposed as a config option. The hard part was plumbing all that, and dealing with complexities like reading it from git attributes at the same time that numcopies is read. Behavior change: When numcopies is set to 0, git-annex used to drop content without requiring any copies. Now to get that (highly unsafe) behavior, mincopies also needs to be set to 0. It seemed better to remove that edge case, than complicate mincopies by ignoring it when numcopies is 0. This commit was sponsored by Denis Dzyubenko on Patreon.
40 lines
1.1 KiB
Markdown
40 lines
1.1 KiB
Markdown
# NAME
|
|
|
|
git-annex numcopies - configure desired number of copies
|
|
|
|
# SYNOPSIS
|
|
|
|
git annex numcopies `N`
|
|
|
|
# DESCRIPTION
|
|
|
|
Tells git-annex how many copies it should preserve of files, over all
|
|
repositories. The default is 1.
|
|
|
|
Run without a number to get the current value.
|
|
|
|
This configuration is stored in the git-annex branch, so it will be seen
|
|
by all clones of the repository. It can be overridden on a per-file basis
|
|
by the annex.numcopies setting in .gitattributes files, or can be
|
|
overridden temporarily with the --numcopies option.
|
|
|
|
When git-annex is asked to drop a file, it first verifies that the
|
|
number of copies can be satisfied among all the other
|
|
repositories that have a copy of the file.
|
|
|
|
In unusual situations, involving special remotes that do not support
|
|
locking, and concurrent drops of the same content from multiple
|
|
repositories, git-annex may violate the numcopies setting. It still
|
|
guarantees at least 1 copy is preserved. This can be configured by
|
|
using [[git-annex-mincopies]](1)
|
|
|
|
# SEE ALSO
|
|
|
|
[[git-annex]](1)
|
|
[[git-annex-mincopies]](1)
|
|
|
|
# AUTHOR
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|