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.
34 lines
874 B
Markdown
34 lines
874 B
Markdown
# NAME
|
|
|
|
git-annex upgrade - upgrade repository layout
|
|
|
|
# SYNOPSIS
|
|
|
|
git annex upgrade
|
|
|
|
# DESCRIPTION
|
|
|
|
Upgrades the repository to current layout.
|
|
|
|
Each git-annex repository has an annex.version in its git configuration,
|
|
that indicates the repository version. If git-annex changes to a new
|
|
layout, you must upgrade the repository before git-annex can be used in it.
|
|
|
|
To see version information, run `git annex version`.
|
|
|
|
Currently, git-annex supports upgrades all the way back to version 0, which
|
|
was only used by its author. It's expected that git-annex will always
|
|
support upgrading from all past repository versions -- this is necessary to
|
|
allow archives to be taken offline for years and later used.
|
|
|
|
# SEE ALSO
|
|
|
|
[[git-annex]](1)
|
|
|
|
[[git-annex-migrate]](1)
|
|
|
|
# AUTHOR
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|