On 27 February 2014 16:18, Stefan Sperling <s...@apache.org> wrote: > On Thu, Feb 27, 2014 at 02:43:50PM +0400, Ivan Zhakov wrote: >> On 26 February 2014 19:48, <s...@apache.org> wrote: >> > Author: stsp >> > Date: Wed Feb 26 15:48:06 2014 >> > New Revision: 1572105 >> > >> > URL: http://svn.apache.org/r1572105 >> > Log: >> > Introduce 'svn auth', a subcommand for managing the authentication cache >> > which supersedes the 'svnauth' tool. Currently, cached credentials can be >> > listed and removed. In the future, this subcommand could also provide a >> > mechanism to add credentials to the cache. >> > >> <bikeshed color="green"> >> May be it's better to call it "svn creds", since this subcommand is >> designated for managing _credentials_, not performing authentication? >> </bikeshed> > > I actually went around the office with the following list: > > svn auth > svn authcreds > svn authinfo > svn authcache > > and asked people what they believed these commands would be used for. > > I was suspecting that 'svn auth' wouldn't be obvious but apparently > it worked out best. In particular because the functionality comprises > usernames/passwords/ssl server certs/ssh client cert pathprases. > > We might also want to extend the functionality of this command in > the future (e.g. 'svn auth --import-ssl-cert', or similar things). > > I agree that 'svn creds' would also work, however in the end it > doesn't really matter as long as the subcommand name is unique > and can be memorized easily. To that end, 'svn auth' works for me > and I'm reluctant to change it without a very compelling reason. I'm not native English speaker, but for me 'authentication' is the process, while this subcommand is about managing objects (credentials).
-- Ivan Zhakov
