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

RE: Subversion Vision and Roadmap Proposal

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Fri, 9 Apr 2010 15:42:51 -0400

> On Fri, Apr 9, 2010 at 10:13, Vadim Chekan <kot.begemot_at_gmail.com> wrote:
> > P.S. Pleeeease, introduce true tags, no more "lets pretend this copy is
> a tag".
>
> What's a "true" tag? What's it good for? How would it behave?

I'm not Vadim but...

Basically an attribute added to a path at a certain revisions. I would think of it sort of like an alias to a revision number. Rather than be a copied path that people can check stuff into. Also, you should be able to float the tag so it stays at head... or move if from one revision to another.


> CVS, on the other hand implemented tags in a fashion that was very
> different. Tags were effectively like labels that you could apply to
> particular versions of particular files. You can tag incrementally,
> marking files as they became "ready". This approach is file-centric
> and doesn't mesh well with the atomic, whole-tree model of versioning
> presented by Svn, Hg, Git, Bzr.

well, this is like I described above, but instead of attaching to a file it is attached to a revision.

Having this would allow me to get a "tag" for example...

svn co ^/MyProject tag="Release 1.0.0" or
svn export ^/MyProject tag="Release 1.0.0"

svn would simply figure out that this was /MyProject/trunk_at_1234 for example.

This would also mean if someone tried to commit a co from a tag they would get a "Your not up to date dummy" message.

BOb
Received on 2010-04-09 21:41:57 CEST

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