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.
> 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
How do you handle errors encountered in performing the upgrade?
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.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-08-03 22:08:45 CEST