RE: Future support to real tags and real branches?

>>>> 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.

Personally, I never do a switch for three reasons...

1. It is alot to type.
2. Pending changes can be mis-commited
2. It is easy to be confused as to which SVN path your project is currently pointing to. Perhaps I am simple minded.

What I do it check out the trunk and branch(es) needed to my local drive in a peer folder:

For example, I check out http://myservername.com/myrepo/myproject/trunk to
~/Projects/MyProject/trunk

I check out http://myservername.com/myrepo/myproject/branches/Feature1 to
~/Projects/MyProject/Feature1

So, now if I am here:

~/projects/MyProject/trunk

My "switch" is as easy as:

cd ../Feature1

ta da! To know what "branch" I am working on I just need to look at the path in the terminal prompt.

BOb

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2425569

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-30 17:58:12 CET