2009/4/2 Dieter Van de Walle <dieter.vandewalle_at_siruna.com>:
> A few weeks ago I got a nice message from TortoiseSVN informing me that
> version 1.6 was released. I happily installed this version.
> However, a soon as TortoiseSVN touched my working copy, it upgraded the
> format of the working copy to it's new version. This is OK if
> TortoiseSVN is your only SVN client, however it is not.
> I am also using a commandline Subversion client running in Cygwin, and
> integrated subversion clients in both Netbeans and Eclipse.
> All of these clients do not yet have 1.6 support, and will probably take
> a while to make this version available. So installing TortoiseSVN
> effectively broke my SVN support in Cygwin, Netbeans and Eclipse.
> Pretty annoying!
This is mentioned in the release notes. Also, you should definitely
not share a working copy with the cygwin client as it is effectively a
> I am aware there is a Python script available to downgrade my working
> copy. However, as soon as I use TortoiseSVN it will upgrade the working
> copy again right?
> So the only option to keep using TortoiseSVN is to downgrade to an older
> version (which I don't want).
> Wouldn't it be a nice feature to be able to prevent TortoiseSVN from
> upgrading the working copy? This would prevent a lot of frustration.
> I don't know how hard this is to implement technically, but it would
> really be a great feature.
> At the very least a user should be warned before upgrading that
> subversion working copies might become inaccessible to other clients.
The upgrade is done by the subversion library, not by TortoiseSVN, so
you have to request this on the subversion mailing list.
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-02 12:31:42 CEST