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

RE: Development practices using Subversion

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-08-11 15:07:47 CEST

"Mads Budde" <mb1@budde.us> wrote on 08/11/2004 02:45:16 AM:

> > implementation of a "move tag/label" command. Subversion does not have
> > move command that operates at the tag level (please correct me if I am
> > wrong
> > - but I haven't found one :-)), so you must implement the same
> > using a two step process (every time you want the label to "float" to
> > desired place that is):
> >
> > 1. delete the old tag (label) from the repository
> > 2. name the desired revision (usually "tip") with the name of the tag
> > deleted.
> >
> > Refer to the "svn delete" and "svn copy" commands for more
> From a subversion implementation perspective tags and branches are the
> same thing, just a copy of "something" made at a certain point in time
> least this is my understanding of it).
> So you should be able to "move" your tag, using the merge command (the
> merge should be trivial). This might not be nice (terminology wise), but
> it should do the trick. If anyone knows a reason why not, please let me
> know.

In my opinion, with the Subversion architecture, you would be much better
off deleting and recreating the tag. This would take up virtually no
space in the repository as well as be simple to do. For example, lets,
say that you do a weekly build and you want to have a tag that refers to
the most recent weekly. You could just do this:

svn delete url://project/tags/weekly -m ""
svn copy url://project/trunk url://project/tags/weekly -m ""


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 11 15:07:49 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.