diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-03-19 18:33:39 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-03-19 18:33:39 -0400 |
| commit | 6a2a17658c1d508cec022132768e9bc1957098d9 (patch) | |
| tree | 0faef3f988c981d35796b6e6f1adfbbbee0e3fa9 /doc/upgrades.mdwn | |
| parent | 43b3675d4298ffe8cfaefed0d70f0ef1fce25e37 (diff) | |
No longer auto-upgrade to repository format 2, to avoid accidental upgrades, etc. Use git-annex upgrade when you're ready to run this version.
Diffstat (limited to 'doc/upgrades.mdwn')
| -rw-r--r-- | doc/upgrades.mdwn | 13 |
1 files changed, 5 insertions, 8 deletions
diff --git a/doc/upgrades.mdwn b/doc/upgrades.mdwn index 1bd97c46e..5c2187c89 100644 --- a/doc/upgrades.mdwn +++ b/doc/upgrades.mdwn @@ -9,15 +9,14 @@ git-annex, and might want to use them with a newer git-annex. ## Upgrade process -git-annex will automatically notice if it is run in a repository that -needs an upgrade, and perform the upgrade before running whatever it -was asked to do. Or you can use the "git annex upgrade" command to -explicitly do an upgrade. The upgrade can tend to take a while, -if you have a lot of files. +git-annex will notice if it is run in a repository that +needs an upgrade, and refuse to do anything. To upgrade, +use the "git annex upgrade" command. The upgrade can tend +to take a while, if you have a lot of files. Each clone of a repository should be individually upgraded. Until a repository's remotes have been upgraded, git-annex -may refuse to communicate with them. +will refuse to communicate with them. Generally, start by upgrading one repository, and then you can commit the changes git-annex staged during upgrade, and push them out to other @@ -54,8 +53,6 @@ Symlinks changed. Also, hashing was added to location log files in .git-annex/. And .gitattributes needed to have another line added to it. -Handled transparently. - ### v0 -> v1 (git-annex version 0.03 to version 0.04) Involved a reorganisation of the layout of .git/annex/. Symlinks changed. |