Quoth Paul Koning <mailto:pkoning@equallogic.com>:
> Tags are (conceptually) not copies; they are symbolic names
> for a revision. CVS gets this right. What Subversion should
> do is to define a mechanism for giving names to a given
> Subversion revision. That would let you do what you want, and
> it would satisfy all uses of tagging I have run into. By
> contrast, the tagging approach that currently exists is
> awkward in some cases, and worse in others. I haven't yet
> run into *any* situation where it felt natural.
Yep. Tags ought to just be aliases for a particular revision number.
Although one advantage of the current scheme is that you can tag a
subfolder rather than the whole of "trunk", which shows a bit more
clearly what the tag is for.
Having said that, when we were using SourceSafe (which supports
fine-grained "labelling" of versions) all we ever ended up doing was
labelling the root of the repository anyway. (Because we have projects
with lots of dependencies, and lots of code shared among multiple
projects.) Now we're using Subversion, it's much the same -- we're
basically just tagging the trunk. So a "named revision" would do just
as well. (In fact, better, assuming all the places that currently
accept revision numbers will also accept names.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 15 04:15:42 2005