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

Re: [PROPOSAL] how to implement 'svn obliterate'

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Wed, 16 Apr 2008 17:31:00 -0400

Blair Zajac <blair_at_orcaware.com> writes:
> Before I read the proposal, I was thinking you would want to run
> obliterate which would create a new repository that one would examine
> before making the new repository the master, so the original would not
> be modified.

We could offer that as an option.

> Also, how would it deal with commits happening using nodes that are
> being obliterated?

The same way it deals with nodes that were already there. (I.e., think
about it and you'll see there's no difference.)

> Also, it seems changing the UUID of the new repository would be a good
> idea to force clients to do a new checkout.

I think that could be an option, but not required: some people don't
want any obvious trace that an obliterate ever happened.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-16 23:31:20 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.