Greg Hudson wrote:
> On Fri, 2002-09-20 at 12:50, Karl Fogel wrote:
>> The trouble is that it's not really related to switch at all. They
>> both affect URLs, but that's about it. Semantically, they are very
>> different operations. (Not sure what the "in this area" meant.)
> "This area" would be manipulations of the wc-repository
> relationship. update, merge, and switch are in the same area.
> Here are my other concerns:
> * "Frob the repository URL in the WC" is a very low-level
> description of what relocate does. How is a tutorial supposed to
> explain the relocate operation to a user who doesn't understand how
> Subversion works at that level?
How about "Change the repository URL in the WC"? Maybe with an
addendum note of "This command only changes the repository URL and
does not use the network."
That doesn't sound too low-level to me. It's what I'd go look for when
I get a mail saying that the repository just changed it's location -
with CVS start writing a perl script to do the job in my working
> * What exactly is the use case for this operation? It sounds like
> it is only supposed to work when you have two repository areas with
> identical contents, but how are you expected to maintain the
> equality of two repository areas? Is "svn relocate" part of some
> hackish, interim form of distributed operation? Will it become
> vestigial if we come up with a more elegant framework for that?
"When your repository URL has changed, you can use this command to
make your working copy point to the new URL." That's enough use case
I've had to use that twice already. Once when I had a portforwarding
setup set up at work when I couldn't use the proxy and then finally
got the proxy working. And the second time was when my external server
changed it's dns name from cs183115.pp.htv.fi to aka.pp.htv.fi - and I
was using SSL for my connections.
In both cases, I had to do 'svn diff > ../safeplace; cd ..; rm -rf wc;
svn co http//...; cd wc; patch < ../safeplace' That sucked.
In a perfect world, every repository is named 'repos.intra.foo.com'
which they can fix to be the repository every time. In the real world,
things like port-forwarding exist, and rewriting urls is what I need.
Though ofcourse I won't care one bit if it's 'svn relocate http://' or
'svn switch --really-only-rewrite-the-damn-urls http://' (even though
it has very little to do with 'svn switch' semantics).
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Sep 21 01:04:46 2002