From: Joseph Myers <joseph@codesourcery.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: GDB <gdb@sourceware.org>, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Stop updating ChangeLog?
Date: Mon, 05 Feb 2018 19:04:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1802051900310.4209@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAH=s-PMDK233mPHHecHbrRky3QyaWYLem8KyujWm+E6M+N1WOQ@mail.gmail.com>
On Mon, 5 Feb 2018, Yao Qi wrote:
> P.S. I found that this topic has been discussed several times in
> various projects (binutils, glibc, etc) without any conclusions. I do
> hope we can make some progress this time :)
All those places are the wrong place for actually effecting any change
other than (c) (generating ChangeLog files at release time having been
permitted by the GNU Coding Standards for over 20 years).
The correct place for discussion of whether the ChangeLog format is useful
generically for GNU projects is the bug-standards list, continuing the
discussion that has been going on intermittently since I started it on 28
July last year. If that discussion results in a GCS change along the
lines I proposed (that is, removing the requirement for ChangeLog format),
then individual projects can consider what commit log format is most
useful for them.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-02-05 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 16:00 Yao Qi
2018-02-05 16:30 ` Simon Marchi
2018-02-05 17:23 ` Dmitry Samersoff
2018-02-05 19:04 ` Joseph Myers [this message]
2018-02-05 21:56 ` Yao Qi
2018-02-05 22:32 ` Joseph Myers
2018-02-06 7:34 ` Joel Brobecker
2018-02-05 19:08 ` John Baldwin
2018-02-05 19:44 ` Andrew Burgess
2018-02-06 21:02 ` Maciej W. Rozycki
2018-02-07 9:11 ` Yao Qi
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=alpine.DEB.2.20.1802051900310.4209@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=qiyaoltc@gmail.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