[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Future support to real tags and real branches?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Wed, 25 Nov 2009 08:35:23 -0600

Marco wrote:
> Hi all,
>
> sorry if the question has been already made, I cannot find trace of that.
>
> I don't know if it's only me, but I really feel SVN is missing support for real tagging and real branches. Having to simulate these features with copies is quite painful, especially when I work with branches. In fact in that case, it's quite clumsy to produce the usual work flow:
>
> - create branch
> - make changes
> - merge from trunk
> - changes
> - merge again from trunk
> - ...
> - switch back to trunk and merge from branch
>
> This work flow currently has to be simulated in SVN by fiddling with revision numbers. To me it's just crazy, it would be much better if SVN understood what branches are and was able to understand the common mean assigned to "merge from X", i.e.: only the last changes from the last merging or creation.
>
> Do the SVN developers plan to support these features in future versions? I really would like they do.
>
> Thanks in advance for a kind reply

Subversion handles having many concurrent working copies checked out out once
simply doing commits and updates to merge all the changes. The only time you
need branches is when you want to keep the changes isolated from each other, as
when you are about to make a release or for large, disruptive changes.

-- 
   Les Mikesell
     lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2424273
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-25 15:36:33 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.