From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <simark@simark.ca>
Received: from simark.ca (simark.ca [158.69.221.121])
 by sourceware.org (Postfix) with ESMTPS id EB457383E82B;
 Wed, 27 May 2020 14:29:10 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org EB457383E82B
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=simark.ca
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark@simark.ca
Received: from [172.16.0.95] (192-222-181-218.qc.cable.ebox.net
 [192.222.181.218])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by simark.ca (Postfix) with ESMTPSA id 618EE1E5F9;
 Wed, 27 May 2020 10:29:10 -0400 (EDT)
Subject: Re: Auto generate ChangeLog for binutils commits?
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>, GDB <gdb@sourceware.org>
References: <CAMe9rOrCaUJZZ+6sme5Z_v4FVKB6mjEAAtdaPXak8WJTgW4Pxg@mail.gmail.com>
 <891ef86a-a47f-18f2-c6bd-e525719e3768@simark.ca>
 <CAMe9rOrdh8Bd=ViMhhXrOuiOEqyVgMbc=M5-q86+ZVdudSwF4Q@mail.gmail.com>
From: Simon Marchi <simark@simark.ca>
Message-ID: <9492d857-c259-1429-f1c7-31a6dbf6510f@simark.ca>
Date: Wed, 27 May 2020 10:29:09 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <CAMe9rOrdh8Bd=ViMhhXrOuiOEqyVgMbc=M5-q86+ZVdudSwF4Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: tl
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-8.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: gdb@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb mailing list <gdb.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/gdb>,
 <mailto:gdb-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/gdb>,
 <mailto:gdb-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Wed, 27 May 2020 14:29:12 -0000

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