man page link fixes
This commit is contained in:
parent
dbb7e81b4f
commit
da55dfc754
4 changed files with 10 additions and 8 deletions
|
@ -56,7 +56,7 @@ Several options can be used to adjust handling of duplicate files.
|
||||||
|
|
||||||
Imports files that are not duplicates. Files that are duplicates have
|
Imports files that are not duplicates. Files that are duplicates have
|
||||||
their content reinjected into the annex (similar to
|
their content reinjected into the annex (similar to
|
||||||
[[git-annex-reinject]]).
|
[[git-annex-reinject]](1)).
|
||||||
|
|
||||||
* `--force`
|
* `--force`
|
||||||
|
|
||||||
|
|
|
@ -29,7 +29,7 @@ The uftp program is used for multicast.
|
||||||
When no files are specified, all annexed files in the current directory
|
When no files are specified, all annexed files in the current directory
|
||||||
and subdirectories are sent.
|
and subdirectories are sent.
|
||||||
|
|
||||||
The [[git-annex-matching-options]] can be used to control which files to
|
The [[git-annex-matching-options]](1) can be used to control which files to
|
||||||
send. For example:
|
send. For example:
|
||||||
|
|
||||||
git annex multicast send . --not --copies 2
|
git annex multicast send . --not --copies 2
|
||||||
|
|
|
@ -159,7 +159,8 @@ elsewhere to allow removing it).
|
||||||
* `standard`
|
* `standard`
|
||||||
|
|
||||||
git-annex comes with some built-in preferred content expressions, that
|
git-annex comes with some built-in preferred content expressions, that
|
||||||
can be used with repositories that are in some [[preferred content/standard groups/]].
|
can be used with repositories that are in some standard groups
|
||||||
|
such as "client" and "transfer".
|
||||||
|
|
||||||
When a repository is in exactly one such group, you can use the "standard"
|
When a repository is in exactly one such group, you can use the "standard"
|
||||||
keyword in its preferred content expression, to match whatever content
|
keyword in its preferred content expression, to match whatever content
|
||||||
|
@ -264,6 +265,8 @@ that git annex get --auto will want to get, and git annex find --want-drop --in
|
||||||
|
|
||||||
<https://git-annex.branchable.com/preferred_content/>
|
<https://git-annex.branchable.com/preferred_content/>
|
||||||
|
|
||||||
|
<https://git-annex.branchable.com/preferred_content/standard_groups/>
|
||||||
|
|
||||||
# AUTHOR
|
# AUTHOR
|
||||||
|
|
||||||
Joey Hess <id@joeyh.name>
|
Joey Hess <id@joeyh.name>
|
||||||
|
|
|
@ -18,11 +18,10 @@ For example:
|
||||||
Without an expression, displays the current required content setting
|
Without an expression, displays the current required content setting
|
||||||
of the repository.
|
of the repository.
|
||||||
|
|
||||||
While [[git-annex-wanted]] is just a preference,
|
While [[git-annex-wanted]](1) is just a preference, this designates content
|
||||||
[[git-annex-required]] designates content that should really not be
|
that should really not be removed. For example a file that is `wanted` can
|
||||||
removed. For example a file that is `wanted` can be removed with
|
be removed with `git annex drop`, but if that file is `required`, it would
|
||||||
`git annex drop`, but if that file is `required`, it would need to be
|
need to be removed with `git annex drop --force`.
|
||||||
removed with `git annex drop --force`.
|
|
||||||
|
|
||||||
Also, `git-annex fsck` will warn about required contents that are not
|
Also, `git-annex fsck` will warn about required contents that are not
|
||||||
present.
|
present.
|
||||||
|
|
Loading…
Reference in a new issue