From: Simon Marchi <simark@simark.ca>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>, GDB <gdb@sourceware.org>
Subject: Re: Auto generate ChangeLog for binutils commits?
Date: Wed, 27 May 2020 10:29:09 -0400 [thread overview]
Message-ID: <9492d857-c259-1429-f1c7-31a6dbf6510f@simark.ca> (raw)
In-Reply-To: <CAMe9rOrdh8Bd=ViMhhXrOuiOEqyVgMbc=M5-q86+ZVdudSwF4Q@mail.gmail.com>
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
next prev parent reply other threads:[~2020-05-27 14:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 17:07 H.J. Lu
2020-05-27 14:10 ` Simon Marchi
2020-05-27 14:20 ` H.J. Lu
2020-05-27 14:29 ` Simon Marchi [this message]
2020-05-27 15:10 ` Auto update ChangeLog for binutils+gdb commits? H.J. Lu
2020-05-29 7:45 ` Martin Liška
2020-05-29 8:51 ` Martin Liška
2020-05-29 12:15 ` Tom Tromey
2020-05-29 12:25 ` Martin Liška
2020-05-29 12:44 ` Tom Tromey
2020-05-29 13:56 ` Martin Liška
2020-05-30 10:23 ` Aktemur, Tankut Baris
2020-05-30 11:22 ` Martin Liška
2020-05-30 19:41 ` Tom Tromey
2020-05-31 4:40 ` Fangrui Song
2020-05-31 7:41 ` Jan Vrany
2020-06-01 7:51 ` Martin Liška
2020-05-29 12:28 ` Martin Liška
2020-05-29 13:57 ` Eli Zaretskii
2020-05-30 19:23 ` Tom Tromey
2020-05-30 19:35 ` Eli Zaretskii
2020-06-01 7:39 ` Martin Liška
2020-06-01 14:59 ` Eli Zaretskii
2020-06-02 6:49 ` Martin Liška
2021-01-15 1:18 ` Fangrui Song
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9492d857-c259-1429-f1c7-31a6dbf6510f@simark.ca \
--to=simark@simark.ca \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).