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

Re: TortoiseSVN Commit improvement suggestion

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 7 Jan 2009 14:42:36 -0500

On Wed, Jan 7, 2009 at 14:33, <Richard_Bordoli_at_xyratex.com> wrote:
> We have a number of development PCs that are shared by our software team. We cache our credentials as it is very painful to type them in fully each time we want to interact with SVN repository. This caching means we often walk up to a machine, do some work and then commit our changes but the commit is recorded as the last person to cache their credentials. I would be very helpful if the TortoiseSVN Commit dialog could show which user account the commit is about to be performed under BEFORE they hit the "OK" button. A further improvement would be to provide the ability to clear the cache at this point (from the commit dialog, rather than firing up the settings dialog) if the commiter is not happy to commit under this account.

What happens if they use the command-line client? Or any other client?
You're only addressing a symptom, not the root of the issue.

If each developer has their own login to the system, this "problem"
goes away. SVN credentials are cached in %APPDATA%, which each system
user account will have its own instance of. This is done in the SVN
libraries, not TSVN.

Sharing WCs between users negates some of the more important reasons
to use version control in the first place. It's best if you fix your
process, not Subversion.
Received on 2009-01-07 20:44:19 CET

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.