From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: simon.marchi@polymtl.ca, binutils@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: Using the vcs_to_changelog.py script
Date: Thu, 13 Feb 2020 19:29:00 -0000 [thread overview]
Message-ID: <834kvuqoar.fsf@gnu.org> (raw)
In-Reply-To: <cba7542898c9be7d4804db274ad1d6f631f8ef9f.camel@skynet.be> (message from Philippe Waroquiers on Thu, 13 Feb 2020 20:09:21 +0100)
> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: binutils@sourceware.org, gdb-patches@sourceware.org
> Date: Thu, 13 Feb 2020 20:09:21 +0100
>
> On Thu, 2020-02-13 at 20:58 +0200, Eli Zaretskii wrote:
> > I have yet to see this accepted as GNU policy. And at least
> > personally, having a ChangeLog in a tarball that just says which
> > function was changed on what date is almost useless to me (and I do
> > sometimes need to work without access to the VCS repositories).
> It looks easy to have a script to generate a file that contains all
> the git log messages + the diff for each commit
> in case detailed changes have to be analysed off-line, without a git repository.
How does this help when all you have is the release tarball?
Anyway, I really don't think we should re-iterate the many months of
discussions on gnu-prog-discuss, which led me to propose the change in
standards.texi. Those discussions have beaten this horse to death,
and I don't think we will invent any new arguments for or against
producing ChangeLog files from VCS logs. If we decide to produce
ChangeLog files at the time the release is tarred, then the ChangeLog
files should be informative and useful; otherwise it's tantamount to
deciding to drop ChangeLog's for the releases as well.
next prev parent reply other threads:[~2020-02-13 19:29 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
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 [this message]
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=834kvuqoar.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
--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).