On Fri, Nov 30, 2012 at 4:05 PM, Ben Reser <ben_at_reser.org> wrote:
> I'm not sure it's something we want to change for everyone. I suspect
> you're the first person that's ever raised any complaints about this.
> This is really a philosophical difference between a centralized
> version control system and DVCS.
> Depending on your repository access setup there are ways around this.
> If the server side knows the value you want to put in svn:author
> instead of the authenticated user name then it's pretty trivial to fix
> with a hook script.
> In my opinion the thing to do here is to allow auto revision
> properties (possibly on a per repo/server) basis. Then we could pass
> along some user configured extra value with each commit and server
> admins could decided to put a hook script in place that puts it in
> svn:author if they wanted.
I would also just say that most software forges that provide SVN
access use the http protocol and it is not difficult or uncommon to
set the author field to an email address when using the Apache server.
It does not necessarily require a hook script to do this. When using
LDAP authentication, as an example, you can simply choose which LDAP
attribute will populate the REMOTE_USER variable which will in turn
Received on 2012-11-30 22:21:30 CET