diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/Is_an_automagic_upgrade_of_the_object_directory_safe__63__/comment_1_c25900b9d2d62cc0b8c77150bcfebadf._comment | 3 | ||||
| -rw-r--r-- | doc/upgrades.mdwn | 13 |
2 files changed, 8 insertions, 8 deletions
diff --git a/doc/forum/Is_an_automagic_upgrade_of_the_object_directory_safe__63__/comment_1_c25900b9d2d62cc0b8c77150bcfebadf._comment b/doc/forum/Is_an_automagic_upgrade_of_the_object_directory_safe__63__/comment_1_c25900b9d2d62cc0b8c77150bcfebadf._comment index 6a34becd3..8420d7bb3 100644 --- a/doc/forum/Is_an_automagic_upgrade_of_the_object_directory_safe__63__/comment_1_c25900b9d2d62cc0b8c77150bcfebadf._comment +++ b/doc/forum/Is_an_automagic_upgrade_of_the_object_directory_safe__63__/comment_1_c25900b9d2d62cc0b8c77150bcfebadf._comment @@ -7,4 +7,7 @@ These are good examples; I think you've convinced me at least for upgrades going forward after v2. I'm not sure we have enough users and outdated git-annex installations to worry about it for v1. (Hoping such upgrades are rare anyway.. Part of the point of changes made in v2 was to allow lots of changes to be made later w/o needing a v3.) + +Update: Upgrades from v1 to v2 will no longer be handled automatically +now. """]] 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. |