[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: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2006-04-10 16:26:00 CEST

Max Bowsher wrote:
> At the moment, svn 1.4 will automatically upgrade WCs when it first
> touches them, after which they become incompatible with svn 1.3.x and
> earlier.
[...]
> In any case, I've been annoyed to find that I've accidentally upgraded
> WCs I didn't want to, and so have a proposal:
>
> I would like to create a new configuration file setting,
> config.[miscellany].allow-wc-upgrade, which defaults to yes, preserving
> the status quo, but which someone who knows that they will be working
> with multiple client versions can set to false, which will cause new
> clients to exit with an error when accessing an old WC, rather than
> silently upgrading it.
>
> Acceptable?

I think that wouldn't solve the problem. Most people would only find out about
the config option after they had encountered the problem of being unable to use
their WC with a v1.3 client after a silent upgrade by a v1.4 client. Unless we
provide a "downgrade" operation, they would be stuck.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 10 16:26:42 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.