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

Re: Enhancement Request: Icon overlays for non-updated working copies

From: Andy Levy <andy.levy_at_gmail.com>
Date: Thu, 4 Aug 2011 06:33:29 -0400

On Wed, Aug 3, 2011 at 22:36, Kevin Radke <kmradke_at_gmail.com> wrote:
> On 8/3/2011 3:08 PM, Andy Levy wrote:
>> On Wed, Aug 3, 2011 at 15:34, Todd Nelson<toddyboy82577_at_gmail.com>  wrote:
>>> If a user installs TortoiseSVN 1.7, any working copies that have not
>>> been upgraded are difficult to find because there are no icon overlays
>>> displayed on the working copy.  It would be beneficial to the users to
>>> put an icon overlay letting the user know they have not updated the
>>> working copy.  You could reuse the same icon for modified or
>>> conflicted files since the limitation on the number of icon overlays
>>> still exists in Windows 7.
>> This was *just* addressed earlier today.
>> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2808881
> I don't really buy the potential performance impact argument. TortoiseSVN
> already knows it is an old working copy because it adds an "upgrade" entry
> to the right click menu...  I found myself manually right clicking on
> multiple folders to remember where all my working copies were located.
>  Without the visual hints of an icon, I'm sure I missed a few too!

Stefan is usually correct about his code.

That discussion is continuing, please follow it.

>>> A utility to search a given disk or path to find all working copies to
>>> upgrade at once would also be useful.  We have developers with a large
>>> number of working copies and unfortunately, they aren't all in the
>>> same parent directory.  Instead of having to manually search for
>>> working copies, this utility would find them all and upgrade them at
>>> once.
>> How do you handle errors encountered in performing the upgrade?
>> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2808880
>> Why can't the developers upgrade their WCs when they're ready?
>> Let's say I'm a split Java&  .NET developer. I've updated TortoiseSVN
>> and AnkhSVN, but I haven't upgraded Subclipse (Subversion plugin for
>> Eclipse) yet. Automatically upgrading *all* of my WCs will immediately
>> break my Java project WCs, at least for usage inside my IDE.
> Nobody is saying you have to upgrade all working copies.  This would simply
> just search the specified locations and say "hey, I found these working
> copies, select the ones you want to upgrade..."

The OP pretty much asked for upgrading all existing WCs.

How do you handle this for unattended/silent installs? Maintain the
current behavior (no upgrades) or silently upgrade them all?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-08-04 12:34:17 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.