From: Jakub Jelinek <jakub@redhat.com>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: [IMPORTANT] ChangeLog related changes
Date: Tue, 26 May 2020 00:48:58 +0200 [thread overview]
Message-ID: <20200525224858.GO8462@tucnak> (raw)
Hi!
I've turned the strict mode of Martin Liška's hook changes,
which means that from now on no commits to the trunk or release branches
should be changing any ChangeLog files together with the other files,
ChangeLog entry should be solely in the commit message.
The DATESTAMP bumping script will be updating the ChangeLog files for you.
If somebody makes a mistake in that, please wait 24 hours (at least until
after 00:16 UTC after your commit) so that the script will create the
ChangeLog entries, and afterwards it can be fixed by adjusting the ChangeLog
files. But you can only touch the ChangeLog files in that case (and
shouldn't write a ChangeLog entry for that in the commit message).
If anything goes wrong, please let me, other RMs and Martin Liška know.
Jakub
next reply other threads:[~2020-05-25 22:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 22:48 Jakub Jelinek [this message]
2020-05-26 5:22 ` Hongtao Liu
2020-05-26 6:08 ` Martin Liška
2020-05-26 6:10 ` Hongtao Liu
2020-06-01 17:24 ` Jonathan Wakely
2020-06-02 6:44 ` Martin Liška
2020-06-02 11:06 ` Jonathan Wakely
2020-06-02 10:55 ` Gerald Pfeifer
2020-06-02 11:05 ` Jonathan Wakely
2020-06-02 11:09 ` Jonathan Wakely
2020-06-02 11:22 ` Jonathan Wakely
2020-06-02 11:48 ` Martin Liška
2020-06-02 13:16 ` Martin Liška
2020-06-02 13:56 ` Jonathan Wakely
2020-06-02 14:06 ` Martin Liška
2020-06-02 14:14 ` Jonathan Wakely
2020-06-02 14:25 ` Martin Liška
2020-06-09 20:29 ` Jonathan Wakely
2020-06-10 7:37 ` Martin Liška
2020-06-10 13:34 ` Tamar Christina
2020-06-10 13:39 ` Marek Polacek
2020-06-10 13:41 ` Martin Liška
2020-06-10 14:53 ` Tamar Christina
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=20200525224858.GO8462@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.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).