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

Re: deleting a tree in the repository

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Thu, 27 Mar 2008 07:35:56 -0400

Geoffrey wrote:
> There's no history to retain. Basically, we've cloned our existing tree
> for a new development effort. It sat idle while the existing tree was
> updated. Now I need to bring them back in sync.

It doesn't sound like you are using SVN the way it was designed. Normally, you
don't [re]import a copy of files that already exist in the repository. You
would instead make a copy inside the repository (which is cheap):

   svn cp http://server/repo/path/original http://server/repo/path/copy

If you are doing this to preserve the history before a large restructuring, by
convention you would do this as a "tag"; if you are doing this in order to
perform that restructuring off the mainline development, by convention you would
call this a "branch". Both tags and branches are completely identical
internally to the repository; they differ only in nomenclature.

On the other hand, if what you are describing is that you imported a tree of
files into the repository, then changed the tree structure itself (but not the
repository), then 'svn rm' and 'svn import' is precisely what you would do. If
you don't have anything else in the repository (i.e. it was only used for this
single project), then it might be cleaner to simply delete and recreate the
repository itself (if you don't care about the history).



To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-27 12:36:04 CET

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.