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

retagging revisions

From: Stein Somers <ssomers_at_opnet.com>
Date: Tue, 15 Sep 2009 13:30:07 +0200

I didn't want to hijack a thread for something that isn't important to me,
but now I'm intrigued.

Suppose I want to have a moving tag e.g. /tags/stable (call it the_tag)
which can "point to" various revisions e.g. in /trunk (call it the_revision).
You can always move the tag by first deleting the_tag and recreating it as a
copy of a new revision, in two transactions.

But in the thread "Move from CVSNT to SVN?", Lorenz writes:
> svnmucc rm the_tag cp revision the_revision the_tag

Indeed a neat way to do it a single transaction. The result is a single
changeset in which the directory the_tag is replaced by a copy of
the_revision. Or I suppose you could bundle multiple replacements in a single

But in the thread "back-end fsfs DB corruption? - attempt to merge uncovering
it", Stefan Sperling writes:

> [...] if a file was replaced within a single revision
> (which can also happen for directories under certain circumstances,
> but which is actually not supported by design in 1.6.x).

So should we shy away from retagging in a single transaction?

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-15 13:31:06 CEST

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.