On Thu, 04 Oct 2007, Karl Fogel wrote:
> Users might at least not feel cheated when their working copy becomes
> un-useable with 1.4 after they touch it with a 1.5 client. Annoyed,
> yes, but many would understand: "Oh, the new version upgraded my
> files, now I can't downgrade. Sigh, okay."
>
> But with the latter behavior, they might use 1.4 and 1.5 clients
> interchangeably for a year, and *then* someone would try out --depth,
> and suddenly that working copy would become unuseable for 1.4 clients.
> "What the heck? We haven't changed our Subversion installation in a
> year! Why did this happen? We didn't change anything, *no fair*!"
I think there's another option that hasn't been mentioned:
When version 1.5 is about to do something that won't work with the old
WC version, it fails with a message like "You need to upgrade your
working copy via 'svn upgrade-working-copy --to-version=10' and then try
this failed operation again; note that upgrading the working copy may
mean that older client software will no longer work".
--apb (Alan Barrett)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 12 23:37:41 2007