On 07/07/2011 04:59 PM, Daniel Shahaf wrote:
> Then why does 'svnadmin upgrade' say
> % $svnadmin upgrade r3
> Repository lock acquired.
> Please wait; upgrading the repository may take some time...
Heheh. Because that message was copy-n-pasted from the one used for
'svnadmin recover'. :-)
I implemented 'svnadmin upgrade' in response to the fact that the project
decided at some point to stop auto-upgrading filesystems when first touched
by a new version of Subversion. As such, the point of 'svnadmin upgrade'
was merely to do the very same steps that the auto-upgrade would have done.
We would never undertake any non-trivial morphing of *repository data* in
an automated, often-unattended fashion! And we already have a sanctioned,
proven mechanism for doing such non-trivial, data-munging upgrades
(dump/load). So 'svnadmin upgrade' merely acts as a trigger for the
no-longer-automatic trivial upgrades required merely to enable
(If folks wish to explore expansion of the feature into the non-trivial
upgrade space, that's certainly something the project can discuss. I'm
merely speaking to the history of the subcommand as it sits today.)
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2011-07-08 17:06:17 CEST