This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: BZ#13592: Fix x86-64 memset


On 04/03/2012 07:05 PM, Andreas Jaeger wrote:

> On 04/03/2012 07:51 PM, Matt Turner wrote:
>> On Mon, Mar 26, 2012 at 6:13 AM, Andreas Jaeger<aj@suse.com>  wrote:
>>> 2012-03-26  Andreas Jaeger<aj@suse.de>
>>>
>>>         * sysdeps/x86_64/memset.S: Fix size paramater comparisions.
>>>         Patch by Michael Matz<matz@suse.de>
>>
>> Does the GNU changelog format specify that the committer, rather than
>> the patch author, should be specified on the line with the date?
> 
> AFAIR practice for glibc so far has been that if a patch comes with a changelog entry, it will go in with the patch. But if somebody else needs to write the changelog entry and also needs to take care of pushing the patch in, he will normally use his name as he takes responsibility for it,


The GNU Coding Standards do say:

<https://www.gnu.org/prep/standards/standards.html#Style-of-Change-Logs>

"When you install someone else’s changes, put the contributor’s name in
 the change log entry rather than in the text of the entry. In other words,
 write this:

2002-07-14  John Doe  <jdoe@gnu.org>

        * sewing.c: Make it sew.

rather than this:

2002-07-14  Usual Maintainer  <usual@gnu.org>

        * sewing.c: Make it sew.  Patch by jdoe@gnu.org.

As for the date, that should be the date you applied the change."

-- 
Pedro Alves


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]