[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb
Subject:    Re: Auto generate ChangeLog for binutils commits?
From:       Simon Marchi <simark () simark ! ca>
Date:       2020-05-27 14:29:09
Message-ID: 9492d857-c259-1429-f1c7-31a6dbf6510f () simark ! ca
[Download RAW message or body]

On 2020-05-27 10:20 a.m., H.J. Lu wrote:
> On Wed, May 27, 2020 at 7:10 AM Simon Marchi <simark@simark.ca> wrote:
>>
>> On 2020-05-26 1:07 p.m., H.J. Lu via Gdb wrote:
>>> Hi,
>>>
>>> I had an impression that ChangeLog was auto generated for GDB commits.
>>> If it is true, should we do the same for binutils commits?
>>>
>>> --
>>> H.J.
>>>
>>
>> No we (GDB) don't do that.  There was a discussion here
>>
>>   https://sourceware.org/pipermail/gdb-patches/2020-February/165728.html
>>
>> But it didn't go anywhere.  Note that when I actually tried the script, it
>> didn't produce good results (perhaps because it wasn't designed with C++
>> in mind).
> 
> GCC will auto generate ChangeLog entry from git commit message.  Can
> binutils+gdb do the same?

Can you please explain what this means?  I suspect that we are not talking about
the same thing.  You mean, still write the ChangeLog entry by hand, but only put
it in the git commit.  And then a script scrapes all the commit messages in order
to produce a ChangeLog file?

Simon
[prev in list] [next in list] [prev in thread] [next in thread]