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
762 B
Markdown
35 lines
762 B
Markdown
# NAME
|
|
|
|
git-annex group - add a repository to a group
|
|
|
|
# SYNOPSIS
|
|
|
|
git annex group `repository groupname`
|
|
|
|
# DESCRIPTION
|
|
|
|
Adds a repository to a group, such as "archival", "enduser", or "transfer".
|
|
The groupname must be a single word.
|
|
|
|
Omit the groupname to show the current groups that a repository is in.
|
|
|
|
There are some standard groups that have different default preferred content
|
|
settings. See <https://git-annex.branchable.com/preferred_content/standard_groups/>
|
|
|
|
A repository can be in multiple groups at the same time.
|
|
|
|
# SEE ALSO
|
|
|
|
[[git-annex]](1)
|
|
|
|
[[git-annex-ungroup]](1)
|
|
|
|
[[git-annex-preferred-content]](1)
|
|
|
|
[[git-annex-wanted]](1)
|
|
|
|
# AUTHOR
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|