On Oct 5, 2007, at 10:55 AM, Ben Collins-Sussman wrote:
> Rather than creating new flags or runtime config options, wouldn't it
> just be simpler to prompt the user before doing an auto-upgrade? I
> mentioned this idea earlier in the thread.
>
> "WARNING: you're using a 1.5 client, and this means upgrading your
> working copy so that it's no longer accessible by older clients. Are
> you sure you want to proceed?"
>
> This will prevent accidents happening from random user
> 'experimentation'. And it means no cryptic errors of things just
> failing, because a user happens to have "auto-upgrade = false" in
> their config file.
When do you envision this prompt happening?
a. whenever a 1.5 client is asked to do anything to a 1.4 WC
b. whenever a 1.5 client is asked to do any write operation to a
1.4 WC
c. whenever a 1.5 client discovers it's just about to do one of the
write operations that actually change the format
I think I prefer b. -- that is, the prompt happens at the beginning
of any susceptible operation, before any changes are done, not half-
way through the operation. "svn update --depth files *" might
process several files (for whom "depth" is innocuous, and I believe
unrecorded in .svn/entries) before it meets its first directory
(where the prompt matters).
As a sort-of implementer of a non-built-in client, I'm having some
qualms about adding additional intra-operation challenges and
dialogs, but I guess I lit off this firestorm, so I'll have to take
some responsibility somewhere or other.
-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 5 20:24:21 2007