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

Re: Automatic upgrading of WC versions and the pain it causes

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2006-04-11 21:01:43 CEST

On 4/11/06, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:
> Er, no. The cleanup comment was just that when the development version
> errors out (instead of borking the working copy), it exits with a lock on
> the wc, which isn't strictly necessary (it hasn't actually modified the
> wc, so it could remove the lock). But it should be a rare occurrence,
> so I don't see that as a big problem.

If you're intending to use this 'not-WC-upgradable' version, doesn't
it mean that everytime you see this error that the WC will no longer
be usable? You won't be able to run cleanup (or any read-only ops)
with the version you have because it'll need to open the WC, right?
-- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 11 21:02:18 2006

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.