Automatic upgrading of WC versions and the pain it causes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

There has been a strong feeling that to require explicit upgrading of
WCs is too wasteful of average user's time.

I don't necessarily agree with that, but perhaps that's because I'm
unable to think myself back into an average user's point-of-view.

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?

Max.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)

iD8DBQFEORrefFNSmcDyxYARAggUAKDUjuwRp1Jad7qlIPg3EPWEY284XACdF/DM
IbB9/IfASNQn6epRQSfo768=
=VjHG
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 9 16:32:31 2006