Was there a reason that 'svn relocate' was designed to not just switch
the containing working copy when you're in a sub-folder of it?
If my current folder is c:\work\foo\bar and my working copy is rooted
at c:\work\foo I can't just 'svn relocate MIRROR_PREFIX
MASTER_PREFIX'.
Oh no, instead svn tells me how it knows the right answer but that I
should be a good doggy and jump through some hoops first...
svn: E155019: Cannot relocate 'C:\work\foo\bar' as it is
not the root of a working copy; try relocating 'C:\work\foo' instead
No shit Sherlock.
It would be nice if invocations with no paths specified just relocated
the entire working copy (the relocation itself is awesome fast though,
thanks WC-NG folks).
NB. Yes I know about the write-through proxies with subversion using
http. No, for internal reasons, switching between our LAN mirror and
our very slow opposite-hemisphere master is necessary, extremely
useful and very frequent.
--
Talden
