mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

man page link fixes

Browse source
This commit is contained in:
Joey Hess 2018-07-06 12:51:18 -04:00
parent dbb7e81b4f
commit da55dfc754
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 10 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/git-annex-import.mdwn
View file

@ -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
their content reinjected into the annex (similar to
[[git-annex-reinject]]).
[[git-annex-reinject]](1)).
* `--force`

2
doc/git-annex-multicast.mdwn
View file

@ -29,7 +29,7 @@ The uftp program is used for multicast.
When no files are specified, all annexed files in the current directory
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:
git annex multicast send . --not --copies 2

5
doc/git-annex-preferred-content.mdwn
View file

@ -159,7 +159,8 @@ elsewhere to allow removing it).
* `standard`
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"
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/standard_groups/>
# AUTHOR
Joey Hess <id@joeyh.name>

9
doc/git-annex-required.mdwn
View file

@ -18,11 +18,10 @@ For example:
Without an expression, displays the current required content setting
of the repository.
While [[git-annex-wanted]] is just a preference,
[[git-annex-required]] designates content that should really not be
removed. For example a file that is `wanted` can be removed with
`git annex drop`, but if that file is `required`, it would need to be
removed with `git annex drop --force`.
While [[git-annex-wanted]](1) is just a preference, this designates content
that should really not be removed. For example a file that is `wanted` can
be removed with `git annex drop`, but if that file is `required`, it would
need to be removed with `git annex drop --force`.
Also, `git-annex fsck` will warn about required contents that are not
present.