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

Re: svn commit: propchange - r30004 - svn:log

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Sun, 23 Mar 2008 13:15:50 -0400

Stefan Sperling <stsp_at_elego.de> writes:
>> Property diff:
>> --- old property value
>> +++ new property value
>> @@ -11,8 +11,8 @@ first address happens to be IPv6 loopbac
>> configured to reject any IPv6 packets.
>> See http://svn.haxx.se/dev/archive-2008-03/0605.shtml
>>
>> -Patch by: Joe Orton <joe_at_light.plus.com>
>> -(Updated for current trunk by me. Got his email from the COMMITTERS file).
>> +Patch by: joe
>> +(Updated for current trunk by me.)
>
> So I guess that means we always list full committers by only
> their tigris.org nick?

Typically, yes -- not just global committers, but any committer, area
committers too. It's not a big deal, though. The reasons I think
committer nick is better are:

   - Adds one level of indirection, so if they change their email
     address in COMMITTERS, all the log messages are still up-to-date.

   - Makes identity unification easier. As you know, contribulyze.py
     tries to fold together all the variants of the same person
     (sometimes just the email address appears, sometimes just the name,
     sometiems both). But this process is heuristic, not perfectly
     reliable. By using nick whenever available, we increase the
     reliability for those people, at least.

Hmmm, maybe http://subversion.tigris.org/hacking.html#crediting should
mention all this?

(Btw, I just used 'M-x svn-hacking-url' from tools/dev/svn-dev.el to
enter the above URL, and it saved me a lot of time. Try it out,
everyone!)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-23 18:22:41 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.