RE: auto-upgrade of working copy
> I have repeatedly heard similar complaints and would therefore
> an explicit 'svn upgrade' upon 1.x to 1.y upgrades for working
> starting with 1.7. And I have never heard anyone asking for the
> feature to be kept.
> The CLI client can print an error. GUI clients can show a window
> the user whether to run an upgrade or bail out.
> This does not harm people using a single client much, but helps
> who use several clients simultaneously a lot (they don't have to
> fresh WCs to continue getting work done).
> We could also add a configuration option to ~/.subversion/config
> causes working copies to always be auto-upgraded, defaulting to
I know this isn't a democracy, but if you are looking for votes this does seem like a more reasonable way to handle it. Especially in keeping with the goal of "not changing your data unless you tell it to" meme.
Received on 2010-07-01 16:11:44 CEST
This is an archived mail posted to the Subversion Dev