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

Re: How to undo multiple moves without a working copy?

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Wed, 10 Jun 2009 23:28:15 -0500

On Jun 10, 2009, at 05:50, Andrey Repin wrote:

> Greetings, Ryan Schmidt!
>> Yes, this problem can be solved by using admin commands like dump and
>> load, but I do not recommend that for this case. It would be like...
>> redecorating a house, then deciding you didn't like it, and
>> bulldozing the house and building it again and decorating it the way
>> it originally was.
> It wasn't decoration, devastating hurricane would be more appropriate
> comparison.
> These changes was not expected, nor wanted, and there's no point to
> keep them
> in repository.
> Not that I'm arguing about doing so with every mistake you making,
> but such
> big troubles need more serious treatment. On both social and
> technical level.

I continue to disagree that there is any need for this drastic action.

The inconvenience it will cause is: 1) Repository downtime while the
administrator dumps, possibly filters, then loads. If the repository
is large, this can take a lot of time, even days. 2) The new
repository UUID must be different than the old one, which means
everybody has to throw out their working copies and check out new
ones. If anybody had uncommitted changes, they must manually move
these over to a new working copy.

Why impose these hardships on your team when you can avoid them
entirely by simply undoing the original change using merge or mv?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-11 06:29:14 CEST

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