This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Use "Regenerated" in ChangeLog entries.
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Sun, 26 Feb 2012 13:34:33 -0500
- Subject: Use "Regenerated" in ChangeLog entries.
- Authentication-results: mr.google.com; spf=pass (google.com: domain of patofiero@gmail.com designates 10.236.170.130 as permitted sender) smtp.mail=patofiero@gmail.com; dkim=pass header.i=patofiero@gmail.com
Developers,
There was a recent discussion here:
http://sourceware.org/ml/libc-alpha/2012-02/msg00581.html
Regarding the use of "Regenerated" entries in a ChangeLog
for files that are regenerated from a canonical source.
The consensus was that it was:
* a well-established convention to use regenerated entries
and that it should not change without some discussion.
* useful to have the regenerated entry to show that the
committing developer acknowledged the file was regenerated
* and that it was easy for others to review that fact.
Given that it was identified as a well-established
convention I have updated the the contribution
checklist here:
http://sourceware.org/glibc/wiki/Contribution%20checklist#Properly_Formatted_GNU_ChangeLog
Without any further discussion I'm going to assume that
we will continue to use regenerated entries in ChangeLogs.
Cheers,
Carlos.