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 22:32:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1802052228210.19606@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAH=s-PPgZTXASC3pFxvn8TmA1SYRq1K80tAKwwSNvoS193tF8A@mail.gmail.com>
On Mon, 5 Feb 2018, Yao Qi wrote:
> Joseph,
> The format of ChangLog entry is out of the scope of this discussion.
> IMO, each project is free to choose whether to write changelog entry
> or not (either in commit log or ChangeLog file). Some GNU projects
I don't believe they are so free (yet). The current (and problematic) GCS
requirement, that I've been trying to get changed, is for ChangeLog files
in releases, using a particular format (which I don't think is a good
format since it forces description at the level of changed to individual
files and named entities therein, which closely duplicates the information
in the diffs themselves) - the projects may choose whether that's a
checked-in file or generated automatically.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-02-05 22:32 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
2018-02-05 21:56 ` Yao Qi
2018-02-05 22:32 ` Joseph Myers [this message]
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.1802052228210.19606@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