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

svn login (was: Re: [PATCH] default to --no-auth-cache)

From: Dominik Westner <westner_at_logicunited.com>
Date: 2003-01-14 12:11:20 CET

Ok, I was reading this thread with great interest as I was concerned
about the default setting aswell.

Why don't we just factor out the caching of login and password into a
separate command, something like

svn login

If I call it I get a warning that my password and login name will be
cached for future use.

I can clear the auth-cache anytime by doing something like

svn login --clear

If I have the auth-cache set with svn login I won't get asked for the
password (specifying --no-auth-cache will circumvent the cache),
If I don't have it set any svn command requiring authentication will
prompt for login and password.

It could be done also on a more fine grained level like

svn login --no-password

will only cache the login but not the password.

But in general I think we should let the user decide if they want to
cache the auth information or not on a working copy basis.
By factoring this out into a separate command should make it very clear
  to the user.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 14 12:28:53 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.