From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: mliska@suse.cz, simark@simark.ca, hjl.tools@gmail.com,
binutils@sourceware.org, gdb@sourceware.org
Subject: Re: Auto update ChangeLog for binutils+gdb commits?
Date: Sat, 30 May 2020 22:35:29 +0300 [thread overview]
Message-ID: <83h7vxkygu.fsf@gnu.org> (raw)
In-Reply-To: <87367hrzua.fsf@tromey.com> (message from Tom Tromey on Sat, 30 May 2020 13:23:57 -0600)
> 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.
next prev parent reply other threads:[~2020-05-30 19:35 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
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 [this message]
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=83h7vxkygu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mliska@suse.cz \
--cc=simark@simark.ca \
--cc=tom@tromey.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).