Re: [PATCH] optionally use $SVN_USERNAME as login
>Mark Benedetto King <email@example.com> writes:
>>>>Okay, I can't argue with this because it /would/ be sufficient, but what
>>>>I *can* say is that always accepting --username is not necessarily the
>>>>right thing to do. Should we also always accept --editor-cmd? No,
>>>>because we have $SVN_EDITOR...
>>>And I do consider $SVN_EDITOR to be a mistake. Note that we also
>>>understand $EDITOR and $VISUAL, and that's fine, because they are
>>>considered standard ways of defining the default editor on Unix.
>>>I'd be much obliged if you'd revert r15393 until we setlle this issue.
>There hasn't been much more discussion. Do people still want r15393
>(makes Subversion understand the $SVN_USER env variable) to remain
>reverted? I'd like to see it reinstated. I think it is useful,
>because it helps people do working copy sharing more smoothly.
I still don't understand what's wrong with our current credentials
caching? It does exactly what you want, on a per-repository basis rather
than globally. Maybe we should consider changing the auth provider code
to always cache the username if it was given on the command line, even
if the server doesn't require authentication.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Aug 17 21:44:01 2005
This is an archived mail posted to the Subversion Dev