Re: tags vs. branches

Could you clarify a bit about how your suggestion below is
similar/different to the approach that Accu-Rev uses (see
http://www.accurev.com). In Accu-Rev, darn near everything
is a "stream" (a project/repository wide branch). Even
"tags" (or "labels") seem to be streams (I think Accu-Rev
calls them "static" streams as opposed to dynamic ones).
Then there is also the notion of a "virtual" stream, which
seems hard to follow.

I'm curious as to how well the stream-model of Accu-Rev (where
everything is a stream - almost) differs from the workspace-model
of Bitkeeper (where everything is a workspace - almost) and how
each does/doesn't fit the branching model intended for Subversion
and how it wants to do tags and branches.

--
Brad Appleton <brad@bradapp.net> www.bradapp.net
  Software CM Patterns (www.scmpatterns.com)
   Effective Teamwork, Practical Integration
"And miles to go before I sleep." -- Robert Frost
On Tue, Sep 02, 2003 at 05:14:49PM +0200, Alexander Mueller wrote:
> Well. The discussion of the differences between tags and branches has
> been discussed a couple of times in the mailing lists.
> 
> The main difference appears to be the "final" status: branches are
> a line of development while tags are markers to a single revision.
> 
> Different possibility haven been discussed how to get tag functionality.
> Just one example:
>   set up a pre-commit hook that forbids comming to an already
>   existing tag
> 
> But how about this:
> - introduce a new property svn:final. If this is true/1 then no changes
> can be commit to the files that have this property set
> 
> - set this property either manually or with svn cp command:
>   svn cp -r1234 --final http://svnserver/svn/myproc/trunk  \
>     http://svnserver/svn/myproc/tags/0.11
> 
> - when copying files will lose the svn:final flag. This way you
>   can copy a tag into a branch a will be able to commit changes to
>   the branch
> 
> - files/dirs with svn:final property still can be deleted
> 
> Xela
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org