why does svn upgrade contact the server?
Before several years we had a HDD crash and lost part of our svn history.
Now we have old projects (we have many customer-individual projects) where
we only have the working copy. This WC refers to an old svn server, it
cannot be switched because the WC head revision has been lost. Till svn 1.6
we could use svn diff to see changes that we implemented after the initial
crash. With 1.7 this doesn't work anymore because svn refuses to upgrade the
WC because it cannot contact the old server.
I found that here http://blogs.collab.net/subversion/ (section "Subversion
1.7 Q & A, part 1") is stated regarding svn upgrade: "This is a local
metadata storage change only, though. 'svn upgrade' does not contact the
server and does not modify the content of the users' working files."
So why my svn tries to contact the server at all?
Received on 2011-12-15 12:04:38 CET
This is an archived mail posted to the Subversion Users