From: Tom Tromey <tom@tromey.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Tom Tromey <tom@tromey.com>, "H.J. Lu" <hjl.tools@gmail.com>,
Simon Marchi <simark@simark.ca>, GDB <gdb@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: Auto update ChangeLog for binutils+gdb commits?
Date: Fri, 29 May 2020 06:44:30 -0600 [thread overview]
Message-ID: <87o8q6c3m9.fsf@tromey.com> (raw)
In-Reply-To: <e3e50047-402c-1f9f-6e94-bc67e3242952@suse.cz> ("Martin =?utf-8?Q?Li=C5=A1ka=22's?= message of "Fri, 29 May 2020 14:25:05 +0200")
Martin> For generation of ChangeLog template, you can use:
Martin> https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=contrib/mklog.py;h=243edbb15c522169709902b27a8558c6e0755107;hb=HEAD
Can it be used without manual intervention?
Or do I still have to edit in all the function names?
Could you run it on some recent gdb commits and show the output?
Martin> About the merges: it's a pain to make a backport (a.k.a) as you're very likely
Martin> conflict in ChangeLog entries. Having the ChangeLog entries in message one
Martin> can do simple git cherry-pick and it's done.
This is emphatically not the case for me.
Martin> About the date-updating: it's also pain to always update a timestamp before
Martin> a patch is installed.
What I'm saying is that it isn't a pain. It's a single command before
pushing. I can't remember the last time the scripts failed but it's
surely been more than 5 years.
I write a lot of patches in gdb and I have already filed off as many
annoying parts as I could -- which is why my default stance is not to
want to change. Changing implies that maybe I'd have to redo this work.
Tom
next prev parent reply other threads:[~2020-05-29 12:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 17:07 Auto generate ChangeLog for binutils commits? 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
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 [this message]
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=87o8q6c3m9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mliska@suse.cz \
--cc=simark@simark.ca \
/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).