As I understand this feature should first be requested from the SVN
library developers.
Should this be some sort of a global setting
(AllowSilentWorkcopyUpgrade = true/false) that is set to true by
default (so it doesn't break compatibility) and an extra method
UpgradeWorkcopy that does the migration?
This way newer TSVN can set the flag to false, and when the "version
upgrade required" error occurs, it can offer the choice to the user
and perform the upgrade explicitly.
Yuri
On May 2, 4:04 pm, "Simon Large" <simon.tortoise..._at_googlemail.com>
wrote:
> 2008/5/2 Andy Levy <andy.l..._at_gmail.com>:
>
>
>
> > On Fri, May 2, 2008 at 12:24 PM, Yurik <yuriastrak..._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.
>
> Correct. TSVN doesn't even know the upgrade is happening as it takes
> place somewhere in the depths of a Subversion library call.
>
> There is a python script on the subversion website which will allow
> you to downgrade a WC to 1.4 format if it gets upgraded by mistake.
>
> http://svn.collab.net/repos/svn/trunk/tools/client-side/change-svn-wc...
>
> Simon
>
> --
> : ___
> : oo // \\ "De Chelonian Mobile"
> : (_,\/ \_/ \ TortoiseSVN
> : \ \_/_\_/> The coolest Interface to (Sub)Version Control
> : /_/ \_\http://tortoisesvn.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr..._at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-h..._at_tortoisesvn.tigris.org
---------------------------------------------------------------------
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-03 20:10:59 CEST