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

Re: replace a tag with a new version

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-03-02 17:38:30 CET

On Mar 2, 2005, at 9:55 AM, Zieg, Mark wrote:

>>> How would you replace tags/current?
>> The short answer is "you wouldn't."
>> The thing you're wanting to do -- find out which tag represents the
>> current stable code -- is something we're handling outside of
>> Subversion.
> I don't understand this answer. Regardless of whether or not the
> procedure is regarded as "philosophically pure" from the "Subversion
> viewpoint" -- if there is such a thing -- is there anything technically
> impossible, unsafe, or inefficient with simply deleting the old
> "tags/stable" tag and copying a new one?

There's nothing wrong with doing that.

> I understand that the fundamental role of a tag is to record "a
> snapshot
> in time." However, it is extremely common user requirement to access
> the most recent "snapshot in time" _at_which_ a certain condition was
> true (the code compiles, or the code passes regression test, or the
> documentation was signed off by QA, whatever). I don't see the "sin"
> in
> maintaining a single, guaranteed-available tag associated with the
> latest snapshot meeting such conditions.

I think what folks are trying to say is: if a 'tag' is constantly
being re-defined, then it's not really a tag, right? It's a branch.

So rather than constantly deleting/recreating a tag, it's more
Subversion-y to just have a 'stable' branch. Whenever the trunk gets
to a 'stable' taggable state, merge the latest trunk changes to the

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 2 17:42:33 2005

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.