From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: switch to autogenerated ChangeLog files
Date: Mon, 11 Jan 2021 14:54:39 -0500 [thread overview]
Message-ID: <f513051a-b234-1122-0c3e-01550d8544b9@polymtl.ca> (raw)
In-Reply-To: <20210111193830.GT7494@vapier>
On 2021-01-11 2:38 p.m., Mike Frysinger wrote:
> to be clear, it isn't generating entries exactly like we write. it's
> using the git commit logs with formatted dates. so i don't think this
> applies exactly anymore. so it's inline with the GNU's VCS principles:
> https://www.gnu.org/prep/standards/html_node/Change-Logs.html
> (and that also recommends just using gitlog-to-changelog).
Oh ok, I confused that script with vcs-to-changelog then!
https://www.gnu.org/software/gnulib/manual/html_node/VCS-To-ChangeLog.html
Just for reference, here's an excerpt of what vcs-to-changelog generates
for the patch I am currently working on:
* gdb/infrun.c: Modified.
(do_target_resume): Modified function.
(restore_thread): Modified.
(for): Modified function.
(check_multi_target_resumption): Modified function.
(gdb_assert): Modified.
(save_defer_tc): Remove.
(maybe_commit_resume_all_process_targets): Remove.
(release): Modified.
(return): Modified.
(gdb_assert): Modified.
(if): Modified function.
(return): Modified.
(return): Modified.
(return): Modified.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(gdb_assert): Modified.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(gdb_assert): Modified.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(if): Modified function.
(if): Modified function.
... and that goes on ...
Hopefully that explains why I said "horrible results" :).
Simon
next prev parent reply other threads:[~2021-01-11 19:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 3:37 [PATCH 1/3] src-release: fix indentation Mike Frysinger
2021-01-10 3:37 ` [PATCH 2/3] gnulib: import gitlog-to-changelog Mike Frysinger
2021-01-11 11:06 ` Andrew Burgess
2021-01-10 3:42 ` [PATCH] sim: switch to autogenerated ChangeLog files Mike Frysinger
2021-01-11 11:05 ` Andrew Burgess
2021-01-11 17:00 ` Simon Marchi
2021-01-11 17:10 ` Luis Machado
2021-01-11 17:31 ` Christian Biesinger
2021-01-11 19:38 ` Mike Frysinger
2021-01-11 19:54 ` Simon Marchi [this message]
2021-01-11 20:35 ` Mike Frysinger
2021-01-12 10:47 ` Andrew Burgess
2021-01-12 18:14 ` Joseph Myers
2021-01-12 18:27 ` Eli Zaretskii
2021-01-12 18:40 ` Eli Zaretskii
2021-01-12 21:27 ` Mike Frysinger
2021-01-12 21:22 ` Mike Frysinger
2021-03-09 5:51 ` Mike Frysinger
2021-03-09 9:42 ` Andrew Burgess
2021-03-17 14:22 ` Luis Machado
2021-01-12 23:20 ` [PATCH 1/3] src-release: fix indentation Mike Frysinger
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=f513051a-b234-1122-0c3e-01550d8544b9@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/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).