8d8e044458
Seems unlikely to be very useful, but trivial. Sponsored-By: the NIH-funded NICEMAN (ReproNim TR&D3) project
60 lines
1.6 KiB
Markdown
60 lines
1.6 KiB
Markdown
# NAME
|
|
|
|
git-annex upgrade - upgrade repository
|
|
|
|
# SYNOPSIS
|
|
|
|
git annex upgrade
|
|
|
|
# DESCRIPTION
|
|
|
|
Upgrades the repository to the latest version.
|
|
|
|
Each git-annex repository has an annex.version in its git configuration,
|
|
that indicates the repository version. When an old repository version
|
|
becomes deprecated, git-annex will automatically upgrade it
|
|
(unless annex.autoupgraderepository is set to false). To manually upgrade,
|
|
you can use this command.
|
|
|
|
Sometimes there's a newer repository version that is not the default yet,
|
|
and then you can use this command to upgrade to it.
|
|
|
|
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.
|
|
|
|
# OPTIONS
|
|
|
|
* --autoonly
|
|
|
|
Only do whatever automatic upgrade can be done, don't necessarily
|
|
upgrade to the latest version. This is used internally by git-annex.
|
|
|
|
* `--json`
|
|
|
|
Enable JSON output. This is intended to be parsed by programs that use
|
|
git-annex.
|
|
|
|
* `--json-error-messages`
|
|
|
|
Messages that would normally be output to standard error are included in
|
|
the JSON instead.
|
|
|
|
* Also the [[git-annex-common-options]](1) can be used.
|
|
|
|
# SEE ALSO
|
|
|
|
[[git-annex]](1)
|
|
|
|
[[git-annex-migrate]](1)
|
|
|
|
Upgrades procedures and history: <http://git-annex.branchable.com/upgrades>
|
|
|
|
News and release notes: <http://git-annex.branchable.com/news/>
|
|
|
|
# AUTHOR
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|