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

Re: CVS/SVN comparison

From: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2004-10-24 02:40:43 CEST

On Oct 23, 2004, at 5:24 AM, Jeremy Pereira wrote:

> What is a tag? It's a copy of a module at a particular point in its
> life cycle.
>
> Seen this way, the appalling hack that is CVS tags becomes obvious.

I disagree with your definition of tag. I view a tag as a 'label' is
in VSS, a label is not a copy. A label marks the repository at a
particular time. I can make a copy of the trunk without subversion's
copy feature if I want. But I can't put a label on the trunk at a
particular time in its development, subversion doesn't appear to
support that. Moving the label to a different revision should be
possible but hard to do my mistake.

> If I decide to move a tag in CVS, nowhere is it recorded why I did it,
> when I did it or even that it was me that did it.

But the problems go deeper than that. When you make a tag and then
commit to it, where is it recorded which revision of the tag is the
"real" version? I.e. If I make a tag called "Release 1.0", but then
someone commits to it, was "Release 1.0" the first revision of the tag,
or the later revision?

I have no problem with the implementation of tags as cheap copies, but
the interface could be improved out-of-the-box if subversion had
built-in support for read-only copies and the link between the copy and
the original was more obvious. A history of the trunk should show when
tags were made and what the paths to those copies are, if it doesn't
then the trunk really isn't tagged is it?

Scott
(I really will stop posting to this thread eventually)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Oct 24 02:41:12 2004

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.