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

Re: svn commit: r1572105 - in /subversion/trunk/subversion: svn/auth-cmd.c svn/cl.h svn/svn.c tests/cmdline/getopt_tests_data/svn--help_stdout tests/cmdline/getopt_tests_data/svn_help_stdout

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Thu, 27 Feb 2014 13:54:49 +0000

Ivan Zhakov wrote on Thu, Feb 27, 2014 at 17:48:42 +0400:
> On 27 February 2014 17:37, Stefan Sperling <stsp_at_elego.de> wrote:
> > On Thu, Feb 27, 2014 at 02:06:38PM +0100, Stefan Sperling wrote:
> >> Also note that the help text mentions 'credentials' for this reason:
> >> auth: Manage cached authentication credentials.
> >
> > Another thing makes me wary about renaming the command right now
> > is that we might still extend the command's functionality, for 1.9
> > or even later.
> >
> > For instance, we could add an 'authentication' mode to this command,
> > which simply completes the authentication process for a given URL and
> > caches the credentials. Then the current name would be very suitable.
> That's exactly what I would like to avoid: pre-authentication will be very
> confusing for users IMHO. Some of them may decide that this is
> required/recommended workflow for Subversion.

It would be a very useful feature. Have you ever configured a cron job
that runs 'svn update' on a password-protected working copy? And then
needed to change the cron job's password? 'svn credentials add' is
exactly what I needed when I did that.

That said, though, you don't have to agree. We aren't discussing
whether to create an 'add' subcommand --- we are discussing whether 'svn
auth' should be renamed. I am leaning towards a "Yes" on that question.
Received on 2014-02-27 14:55:42 CET

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.