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

Re: RFC: simple proposal for Internet-scoped IDs

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: Sat, 1 Dec 2012 09:08:05 -0500

On Sat, Dec 1, 2012 at 8:53 AM, Eric S. Raymond <esr_at_thyrsus.com> wrote:

> I'm not certain, but if your server-side hooks work the way I think
> they do, all of this except (1) can be done in Python. Not having to
> add complexity to your C code is a significant virtue.

Here's another approach to take with regards to setting the FULLNAME field
that doesn't require any change to the client and can be deployed
server-side via hooks without any code changes at all. So, (1) can be done
in Python pretty easily for the lazy users and coders who don't want to do
anything at all. =)

If you have a centralized registry (like either LDAP or
http://people.apache.org/committer-index.html), the server in the
server-side hooks can set FULLNAME for each svn:author if isn't set by the
client by looking up its internal directory. Within the ASF
infrastructure, we have tools to allow committers to manage fields like
this in a self-service way. So, the server admin can default that field as
they like and give the users to set that field as they like.

I believe that this is one of the benefits of a centralized infrastructure
- we can make it so that every client doesn't *have* to set something
themselves on their client to utilize FULLNAME.

And, once again, I'll reiterate my earlier point that FULLNAME can be added
retroactively pretty easily to existing SVN repositories. So, for
svn.apache.org, after we might deploy a FULLNAME infrastructure, we could
easily craft a tool to go back to all old revisions and annotate them
correctly. Easy peasy. -- justin
Received on 2012-12-01 15:08:40 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.