Auto update ChangeLog for binutils+gdb commits?

Martin Liška mliska@suse.cz
Mon Jun 1 07:39:08 GMT 2020


On 5/30/20 9:35 PM, Eli Zaretskii wrote:
>> From: Tom Tromey <tom@tromey.com>
>> Cc: Tom Tromey <tom@tromey.com>,  mliska@suse.cz,  simark@simark.ca,
>>    hjl.tools@gmail.com,  binutils@sourceware.org,  gdb@sourceware.org
>> Date: Sat, 30 May 2020 13:23:57 -0600
>>
>> Eli> Having the names of the functions in the log is one of the most
>> Eli> important reasons for following the ChangeLog format.  If it were not
>> Eli> for that reason, we could let people write free-text log messages,
>> Eli> because file names are easily gleaned from the VCS log.
>>
>> If the mklog script works, then the function names are also easily
>> computed from the diff.
> 
> If all the script does is look at the hunk headers of the diffs, then
> indeed such a script doesn't have any added value.  I thought it did a
> more thorough (and thus more accurate) job than that.
> 

It does, it tries to find a function name, macro, struct in a diff hunk
and this name is taken as changed. If nothing like this is found, then
diff header name is used.

Martin


More information about the Gdb mailing list