[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: migrate to new server - subversion 1.3.0 -> 1.4.3

From: eg <egoots_at_gmail.com>
Date: 2007-07-04 19:30:18 CEST

Erik Huelsmann wrote:
> On 6/29/07, Andy Levy <andy.levy@gmail.com> wrote:
>> > >
>> > > Or will users have to perform an entirely new checkout of
>> > > the repos from the new hardware?
>> > >
>> >
>> > The users will also have to upgrade to 1.4.x clients if you upgrade
>> the
>> > repository to 1.4.x
>>
>> I think that's only true if you're using file:/// access. Given that
>> Anne is talking about auth and access files, it's safe to assume that
>> she's not (as those don't apply to file:///).

Right. I was also thinking about taking advantage of the new features...
but it sure doesn't read that way :(
If you want the clients to "to get the full benefits" of the new binary
delta encoding improvements added in 1.4, then both client and server
will need to be upgraded to 1.4. In this case, the remaining benefits
would be that your "network traffic becomes smaller and faster".
>>
>> > Besides that, I "think" it should work out of the box.
>> > At worst, you would have to do an svn switch --relocate
>>
What I meant to say was "even if you loaded the repository onto a new
server with a different URL(instead of the same one), then the worst the
users would need to do is an svn switch --relocate. Not a full checkout.

Yikes. Sorry for my badly worded reply here.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 4 19:30:33 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.