I saw the thread below in the list archive. I know it is not a very
polite thing to return to an old conversation, but I would like to
make a question regarding the selected part from Schmidt mail:
"The internal unique ID of the old and new repositories must be the
same (e.g. it must in fact be the same repository that has just moved
somewhere else; you cannot use this to link a working copy of one
repository with a different repository that has a different history
and a different unique ID)."
("old" and "new" could be "A" and "B", I guess.)
My question: would not this (= to allow link different directories
with different IDs) be the base for a private workspace implementation
(something like bitkeeper)? Is the private workspace as a private
repository feature planned for Subversion? I think it is nice feature
to have (not only because I need it).
Cordially,
Emilio.
PS: I know svk...
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
From: Ryan Schmidt <subversion-2007a@ryandesign.com>
Date: Fri, 23 Feb 2007 11:42:25 -0600
Subject: Is there any way to use the switch command cross-repository?
On Feb 23, 2007, at 11:01, James Oltmans wrote:
>>> Is there any way to use svn switch in a way that will go
>>> cross-repository? The code bases in each repository are very
>>> similar but
>>> we're bringing in a project as a branch off the main trunk that was
>>> started as its own repository. I'd like to be able to switch
>>> everyone's
>>> working copies to point at this other repository rather than the old
>>> ones but subversion won't let me.
>>
>> Are you using svn switch or svn switch --relocate?
>
> Hmmm I didn't know about that... but I tried it and that's not working
> either.
> svn switch --relocate http://scm/svn/liberty_server/dev_1.0
> http://scm/svn/bolo/branches/bolo_ui .
> svn: Relocate can only change the repository part of an URL
>
> Does that mean what I'm trying to do isn't going to work?
Suppose your repositories are at http://www.example.com/svn/
"svn switch" is for switching your working copy to a new place in the
same repository. For example, if you have a working copy of
fooproject's trunk, and you now want to work on a barbranch, you
would use "svn switch http://www.example.com/svn/fooproject/branches/
barbranch"
"svn switch --relocate" is for when you've moved your repository to a
different URL, for example the hostname changed from www.example.com
to svn.example.com. Then you would use "svn switch --relocate http://
www.example.com http://svn.example.com". The internal unique ID of
the old and new repositories must be the same (e.g. it must in fact
be the same repository that has just moved somewhere else; you cannot
use this to link a working copy of one repository with a different
repository that has a different history and a different unique ID).
So I would say that no, what you want to do is not possible. People
will have to check out new working copies.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 30 05:04:12 2007