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

Re: Deficiency in Subversion - restore breaks working copies

From: John Locke <mail_at_freelock.com>
Date: 2003-08-14 19:55:31 CEST

Wadsworth, Eric (Contractor) wrote:

>Also, there are some issues not addressed here, such as what about the user
>who didn't send in his working copy until after the admin released the
>"restore" flag, and so is out of sync. And I don't think you can trust
>revision numbers to always be good indicators of state; strange things could
>happen when you get two restores in rapid succession, stuff like that.
>Greater minds than mine will surely find all sorts of holes in my idea. ;)
>
>
>
Yikes! Sounds like a whole mess of new features, a real rat's nest of
issues. If you have to do two restores in rapid succession, it sounds
like you have much bigger problems than broken working copies...

I'm not claiming to have a greater mind, but I'm -1 all over this.

How often do you need to restore a backup? Seems that this is an
extremely rare situation. And there's a relatively simple fix: check out
a new working copy. You can do a simple diff to compare to your old wc,
and move any changes since your last commit. Yeah, it's a pain if
there's hundreds of working copies--but for the frequency of this event,
surely much less than the pain of implementing something that would take
an awful lot of thought and testing to work out all the issues--when
that effort should be used towards reducing the need for restoring a
repository in the first place... And the pain really isn't any more than
resolving any other conflict.

If you implemented some way to have something as huge as restoring a
repository, removing many of the revisions or branches in it, wouldn't
it be better if the users were aware of the change? Otherwise they may
go looking for something (revision, branch) that used to exist but
doesn't anymore, and get really confused.

Seems to me the most that might be necessary is an intelligible error
message when the wc has a higher revision number than the repository.

Now here's a thought--how about adding a URL to error messages that
point to an appropriate page in the SVN Book, with instructions for
working around the specific issue?

Cheers,
John Locke

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 14 19:56:12 2003

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