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

Re: Warning on repository version upgrade

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 2 May 2008 12:58:29 -0400

On Fri, May 2, 2008 at 12:24 PM, Yurik <yuriastrakhan_at_gmail.com> wrote:
>
>
> On May 2, 11:21 am, "Andy Levy" <andy.l..._at_gmail.com> wrote:
>
> > On Fri, May 2, 2008 at 10:57 AM, Yurik <yuriastrak..._at_gmail.com> wrote:
> >
> > > Please add a warning when changing the structure of the checkout
> > > directory to the newer version.
> >
> > > In our team, some of us has already migrated to the bleeding edge of
> > > the TortoiseSVN, while other machines for stability and compatibility
> > > reasons have to remain a bit behind. Unfortunately, sometimes we do an
> > > update on the checkout dir on a remote share, and TortoiseSVN silently
> > > upgrades it, causing numerous problems as there is no easy way to
> > > downgrade it back.
> >
> > > Please warn the user of the upgrade and allow them to cancel it.
> >
> > Cancel the upgrade, or cancel the operation altogether?
>
> Cancel everything. I obviously cannot expect newer version to run on
> the older repository. Its just that when I, for example, open an older
> project in Visual Studio, it offers to convert the project, or cancel
> the operation. I do not expect VS to continue working with the older
> format, yet I do expect it to warn me before ruining the file. This is
> very similar - I do not want irreversible changes that might cause
> problems for other applications.

This sounds like functionality which would need to be exposed by the
core SVN libraries, for use by clients using those libraries.

---------------------------------------------------------------------
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-02 18:58:38 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.