From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: Using the vcs_to_changelog.py script
Date: Thu, 13 Feb 2020 03:37:00 -0000 [thread overview]
Message-ID: <83imkbqhry.fsf@gnu.org> (raw)
In-Reply-To: <fae607e5-7fec-b295-a579-7a8ea7c214da@polymtl.ca> (message from Simon Marchi on Wed, 12 Feb 2020 18:32:51 -0500)
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Date: Wed, 12 Feb 2020 18:32:51 -0500
>
> As you may or may not know, the glibc project has started using a script called
> vcs_to_changelog.py to automatically generate their ChangeLogs. They don't do
> hand-written ChangeLog entries with their contributions. Instead they generate
> a ChangeLog file using that script when creating a release, passing it a range
> of git commits for which to create ChangeLog entries.
>
> I would very much like if we started using this in GDB, and it was suggested
> that we could try to sync with binutils, as you might want to do the same.
>
> Here's how it could work in practice:
>
> 1. We update our gnulib import to import the vcs_to_changelog.py script (it is
> distributed as a gnulib module).
> 2. We update src-release.sh to call the script and generate a single top-level
> ChangeLog that is included in the release tarball.
Several things we'd need to consider if we go this way:
. AFAIK, the script you mention currently supports only C sources;
we'd need to see how well it supports C++
. Some files in our tree are neither C++ nor C: there are Python
files, Guile files, shell scripts, and Texinfo files, to mention
just a few: what to do about them?
. Last, but not least: we'd need detailed instructions for how to
produce the commit log messages under this regime, because the old
conventions will not be valid anymore.
next prev parent reply other threads:[~2020-02-13 3:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 23:33 Simon Marchi
2020-02-13 1:03 ` Alan Modra
2020-02-13 2:29 ` Jeff Law
2020-02-13 3:13 ` Simon Marchi
2020-02-13 14:13 ` Eli Zaretskii
2020-02-13 3:37 ` Eli Zaretskii [this message]
2020-02-13 14:19 ` Simon Marchi
2020-02-13 15:42 ` Eli Zaretskii
2020-02-13 16:26 ` Simon Marchi
2020-02-13 18:58 ` Eli Zaretskii
2020-02-13 19:09 ` Philippe Waroquiers
2020-02-13 19:29 ` Eli Zaretskii
2020-02-13 20:56 ` Simon Marchi
2020-02-13 21:07 ` Simon Marchi
2020-02-14 9:45 ` Eli Zaretskii
2020-02-14 19:31 ` Simon Marchi
2020-02-14 20:16 ` Eli Zaretskii
2020-02-14 21:08 ` Simon Marchi
2020-02-15 7:26 ` Eli Zaretskii
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=83imkbqhry.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.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).