21ec5872f4
i found that most man pages only had references to the main git-annex manpage, which i stillfind pretty huge and hard to navigate through. i tried to sift through all the man pages and add cross-references between relevant pages. my general rule of thumb is that links should be both ways unless one of the pages is a more general page that would become ridiculously huge if all backlinks would be added (git-annex-preferred-content comes to mind). i have also make the links one per line as this is how it was done in the metadata pages so far. i did everything but the plumbing, utility and test commands, although some of those are linked from the other commands so cross-links were added there as well.
35 lines
672 B
Markdown
35 lines
672 B
Markdown
# NAME
|
|
|
|
git-annex wanted - get or set preferred content expression
|
|
|
|
# SYNOPSIS
|
|
|
|
git annex wanted `repository [expression]`
|
|
|
|
# DESCRIPTION
|
|
|
|
When run with an expression, configures the content that is preferred
|
|
to be held in the archive. See [[git-annex-preferred-content]](1)
|
|
|
|
For example:
|
|
|
|
git annex wanted . "include=*.mp3 or include=*.ogg"
|
|
|
|
Without an expression, displays the current preferred content setting
|
|
of the repository.
|
|
|
|
# SEE ALSO
|
|
|
|
[[git-annex]](1)
|
|
|
|
[[git-annex-required]](1)
|
|
|
|
[[git-annex-preferred-content]](1)
|
|
|
|
[[git-annex-groupwanted]](1)
|
|
|
|
# AUTHOR
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|