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

Re: Newbie Question

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-09-01 01:13:43 CEST

On Sep 1, 2006, at 00:59, Ernest L. Williams Jr. wrote:

>>> Are you not surprised that SVN has two commands to perform this
>>> operation where as CVS only required one?
>> Which two commands?
> svn --relocate
> svn update

But those two commands do two completely unrelated things.

"svn update" contacts the Subversion server and asks it to send the
client all the changes that have occurred in the repository since the
last update.

"svn switch --relocate" walks through a working copy and updates its
concept of where the repository is located, and never contacts the
Subversion server.

>> Which operation?
> I just want to do a svn update on an already checked out working copy.
> The problem is that another user checkout the working copy.

Ok, yes, that is the problem. AFAIK Subversion is designed on the
theory that everybody has their own workspace. When you work against
that assumption you sometimes have to do some additional work, in
this case relocate the working copy before a different user can work
with it.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 1 01:15:11 2006

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