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

Re: I'm a long time user with a long time complaint

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 3 Sep 2010 09:06:51 -0400

On Fri, Sep 3, 2010 at 08:47, Loritsch, Berin <bloritsch_at_dtri.net> wrote:
> I love SVN, and TortoiseSVN is a really good integration into Windows.  My
> complaint has to do with Tortoise hijacking the local
> repository—particularly if it wasn’t the tool used to check the code out to
> begin with.  I used to do Java code, and the SVN plugins for the major IDEs
> kept pace with SVN itself and this project.
> Now, I’m developing .Net and I’m not nearly so lucky any more.  The plugin I
> have for Visual Studio uses a different version of the SVN client than
> TortoiseSVN.  It’s a fact of life, it happens.  The problem is that the SVN
> integration with Visual Studio breaks as soon as I touch the local
> repository with Tortoise.  It breaks because the client version in my Visual
> Studio plugin is too old to work with that local repository.  Tortoise SVN
> “upgrades” the local copy on me without warning me, telling me that is what
> it is doing, letting me cancel that decision, or respecting the fact I
> didn’t use Tortoise to check out the code to begin with.
> This is very frustrating.  It’s happened to me at least twice this past
> month.  My only recourse is to blow away the old repository and re-checkout
> the code.  With a checkout that is several hundred MB, that’s a sizeable
> enough amount of time that it is very inconvenient.
> TortoiseSVN breaks the cardinal rule of useful tools: “DO NO HARM”.  Quite
> frankly there are times where I would like to use some of the bug fixes with
> a newer version of TortoiseSVN, but I have to face the problem of dealing
> with the SVN version differences between Tortoise and the IDE plugin I’m
> using.

Nice rant, but you're directing it at the wrong people. This
functionality (the auto-upgrade of the working copy format) is done by
the Subversion libraries themselves. **ANY** client will do the same
thing. And it is intentional. It is incumbent upon the user to manage
the upgrades to his own software.

> How do I turn off this insidious feature?  I don’t want Tortoise touching
> the version of my local repository.  At all.  Not even a little bit.  If
> that means some features don’t work, fine.  As long as checkout, checkin,
> and conflict resolution work I’m fine.

You have directly contradicted yourself. You say you don't want
"Tortoise" touching your working copy, but then you want to use
Tortoise to work with your working copy.

This isn't an "insidious" feature, and it can't be turned off.
Subversion always automatically upgrades the working copy format when
the client is upgraded. This is advertised in the release notes with
every new version.

Don't like it? Don't upgrade your client. You deal with it by keeping
all your clients (AnkhSVN, VisualSVN, Subclipse, Tortoise,
command-line SVN) up to date with the same version of Subversion.

> Confidentiality Note: The information contained in this message, and any
> attachments, may contain proprietary and/or privileged material. It is
> intended solely for the person or entity to which it is addressed. Any
> review, retransmission, dissemination, or taking of any action in reliance
> upon this information by persons or entities other than the intended
> recipient is prohibited. If you received this in error, please contact the
> sender and delete the material from any computer.

Please don't include useless "confidentiality" notices on posts to
PUBLIC mailing lists. It's just a waste of bandwidth.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-03 15:07:48 CEST

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