b184fc490a
Sometimes users would get confused because an option they were looking for was not mentioned on a subcommand's man page, and they had not noticed that the main git-annex man page had a list of common options. This change lets each subcommand mention the common options, similarly to how the matching options are handled. This commit was sponsored by Svenne Krap on Patreon.
44 lines
1.2 KiB
Markdown
44 lines
1.2 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)
|
|
|
|
# OPTIONS
|
|
|
|
* The [[git-annex-common-options]](1) can be used.
|
|
|
|
# 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.
|