Julian Foad wrote:
> Max Bowsher wrote:
>
>> 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.
>
> 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.
Or maybe it's OK that they have to abandon that WC, set the config option, and
then can make a new WC and ... do what with it? Work in it with their old
client only? I don't see the point of that. What exactly are we trying to
achieve? Should svn v1.4 be able to work with old WCs without upgrading them,
so that it can be used in parallel with an older GUI client (for example)? If
so, should it have full functionality or just read-only ability?
- 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 19:38:29 2006