[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: TortoiseSVN-1.5.0-RC2 released

From: Andy Levy <andy.levy_at_gmail.com>
Date: Mon, 12 May 2008 10:46:11 -0400

On Mon, May 12, 2008 at 10:19 AM, Ed Avis <eda_at_waniasset.com> wrote:
> Stefan Küng <tortoisesvn@...> writes:
>
> >We've released a second release candidate of the upcoming 1.5.0 release.
>
> I think the release notes could be even more explicit about the repository
> auto-upgrading:
>
> >This version will upgrade your working copies automatically to the new version.
> >If you have other Subversion clients you use, do not install this release unless
> >you have 1.5.x versions of those clients too. If you only use TortoiseSVN, this
> >is not a problem.
>
> It should say 'if you only use this new TortoiseSVN release and not any older
> TortoiseSVN, this is not a problem'. Upgrading the working copy makes it
> incompatible with the current stable TortoiseSVN release.

One can only install one version of TSVN on a given system in the
first place (aside from maybe Win32 & Win64, in which case most people
already know what they're doing). So wouldn't this be moot anyway,
unless you're sharing a WC with multiple clients PCs/users, which you
aren't supposed to be doing in the first place?

> But IMHO it would be better to prompt before upgrading the working copy rather
> than doing it silently. The prompt only has to appear once, so it wouldn't be a
> hassle for the user.

That functionality would have to be provided in the core SVN libraries
first. I believe this same question was asked in the last week or 2 on
this list.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-12 16:46:16 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.