raw email addresses and ChangeLog entries?

Christopher Faylor cgf-no-personal-reply-please@cygwin.com
Fri Feb 17 21:42:00 GMT 2006

On Fri, Feb 17, 2006 at 03:24:41PM -0600, Brian Ford wrote:
>On Fri, 17 Feb 2006, Corinna Vinschen wrote:
>>On Feb 17 09:52, Brian Ford wrote:
>>>On Fri, 17 Feb 2006, Corinna Vinschen wrote:
>>>>On Feb 16 10:46, Jerry D. Hedden wrote:
>>>>Would you please don't copy raw email addresses in your replies?
>>>>>2006-02-16  Jerry D. Hedden  <jerry at hedden dot us>
>>>I've always been confused about the above dichotomy.  Is it ok to
>>>obfuscate ChangeLog email addresses?  Otherwise, what's the point of
>>>PCYMTNQREAIYR requests in cygwin-patches?
>>Dunno if I'm speaking for Chris here, too, but I usually send patches
>>to other lists without the date/name/email header, for the simple
>>reason that the date will change anyway to the date of checkin.  The
>>name and email address is given in the mail header anyway, so why
>Sounds good.  I'm all for it if cgf agrees.

Sorry, but I don't.  I've even mentioned what I prefer recently, i.e.,
in theory a ChangeLog is supposed to be a cut/paste with no
interpretation.  If I get a patch today, I should be able to just cut
and paste it today without any editing.

AFAIK, ChangeLogs have *always* been an exception to the "don't post raw
email addresses" rule.  Look at the gdb or gcc patches mailing lists.

The "don't use raw email addresses" rule that we try to enforce in the
Cygwin lists is basically a "don't do it because it is stupid and it
causes harm" rule.  There is typically no reason to put a raw email
address in the body of a non-patch message.  There *is* a reason to use
an email address when the email address is supposed to eventually be
recorded in a ChangeLog.

However, this isn't really worth a lot of debate (not that that has ever
stopped anyone in these lists).  It isn't the end of the world if
someone doesn't send their email address but my preference is to get a
complete ChangeLog and that seems to be what most other lists prefer as


More information about the Cygwin-patches mailing list