On Thu, Nov 26, 2009 at 8:32 PM, Ryan Schmidt
<subversion-2009d_at_ryandesign.com> wrote:
> On Nov 26, 2009, at 05:34, Stefan Sperling wrote:
>
>>>>> I know. Progress is trickling in. I'd like (and expect)
>>>>> 'svn switch ../branches/mybranch' to do the obvious instead
>>>>> of giving me 'not a working copy there'.
>
> Actually the error I get is:
>
> svn: '../branches/mybranch' does not appear to be a URL
>
>
>>>> What do you think is obvious?
>>>
>>> Well, switching to a working copy is pointless. So, take the
>>> URL (of svn info) and apply the relativ path given to it,
>>> and switch to that URL.
>>
>> Switch the current working copy to the URL of a different
>> working copy?
>
> No, I think what he wants is:
>
> There is only one working copy, and he is in the directory of that working copy. Its svn URL is, say, http://svn.example.com/subsys/component/module/trunk. He wants to switch the working copy to http://svn.example.com/subsys/component/module/branches/mybranch. He wants to do this by typing as little as possible, e.g.:
>
> svn switch ../branches/mybranch
>
> "../branches/mybranch" is to be taken not as a filesystem path but as a relative URL based on the URL associated with the
> current working copy.
This was added in 1.6 and it is purely a client feature so it works
with an server version. The syntax is:
$ svn switch ^/branches/mybranch
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2424728
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-11-27 02:51:30 CET