[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: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-03-02 12:39:43 CET

On 02.03.2005, at 05:52, Andrew Thompson wrote:

> Say I have tags/current
> In my trunk (or my wc), I've got newer/better "current" code.
> How would you replace tags/current?


The short answer is "you wouldn't."

Of course Subversion doesn't enforce anything at all; "tags" and
"branches" and "trunk" are all just concepts to which a human must
assign meaning for them to have any. Within Subversion, they're all
just copies.

That said, the "Subversion Way" is that tags are copies of a branch at
a specific point in time -- a snapshot, showing how things were at some
point in the past. The "Subversion Way" is that tags never change. Of
course, the system does not prevent you from modifying the contents of
a tag (unless you write a pre-commit hook preventing that). But the
idea is that you release version 1.0.5 of your project, and to do so,
you create a 1.0.5 tag so that in the future, when the current version
is 1.1.7, you can look back at the contents of the 1.0.5 tag directory
to see what your project looked like at version 1.0.5.

The thing you're wanting to do -- find out which tag represents the
current stable code -- is something we're handling outside of
Subversion. Depending on your tagging habits and tag numbering scheme
it could be as simple as listing the contents of the tags directory,
sorting it, and picking the last one. Or you may want to keep track of
it manually.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 2 12:42:15 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.