RE: Re: Future support to real tags and real branches?

> > real tagging
> What did you understand by "real tagging" ?

Like 'tagging that is not simulated by branches that we need to configure readonly'?

Like having some protection against accidentally switching from trunk/subdir to branch/X instead of branch/X/subdir?

> With SVN you can define the meaning yourself...

You usually need to...

...
> Why? They are the faremost fastes branches i ever worked with...I know ClearCase, CVS etc. and all of them are much slower...

You need to widen your horizon. (I'm not going to point to the obvious suspects here.)

1) Because of the "we don't really have branches" you need to type a lot of URLs when doing branches and merges, and a priori nobody keeps you from merging the wrong directory level.

2) svn makes a lot of serial HTTP requests which isn't exactly helpful or fast when you aren't within throwing distance from your server (read: DSL (svn ls takes 0.4s) or GPRS (svn ls takes twelve seconds)).

> > - create branch
> > - make changes
> > - merge from trunk
> > - changes
> > - merge again from trunk
> > - ...
> > - switch back to trunk and merge from branch
>
> This is in my opinion not a "usual" work flow, cause many people using branches in an other way.

Why? Keeping a feature branch in sync with the evolving trunk isn't a bad idea. Except that I wouldn't switch and rather make a separate sandbox for the merge.

...
> In your workflow you are synchronizing the branch with the trunk...the question is, is that really neccesary ?

...
> May be the living time for your branch is too long?

In the perspective of svn allowing everything, that is an orthogonal question.

> On the other hand it means that you synchronize from trunk to branch by using svn merge URL/trunk (with revision ranges)....

Using revision ranges is only required in pre1.5 svn.

...
> > "merge from X", i.e.: only the last changes from the last merging or
> > creation.
> That can be done if you use a branch in "usual" way..and not synchronizing it with trunk.

Acually, and as far as I understand the docs, keeping a branch in sync with the trunk by repeatedd merging is doable with svn (1.5ff), only the backmerge into trunk needs an --reintegrate, and after that the branch is effectively dead, as the mergeinfo is garbled by design at that point.

Andreas Krey

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

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 19:10:25 CET