From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: GDB "Start of New Year Procedure" -- 2018 edition
Date: Mon, 01 Jan 2018 04:48:00 -0000 [thread overview]
Message-ID: <20180101044801.7201-1-brobecker@adacore.com> (raw)
Hello,
I am about to push the following commits. Most of them are a direct
application of the "Start of New Year Procedure" procedure listed
in our GDB Internals Manual. A couple of them are tiny adjustments
to the gdb/copyright.sh script to remove the need for a manual update
of a couple of files that can now be processed automatically, and
before that fix a small bug which is hidden until we remove those
the special processing for those two files.
* [PATCH 1/5] Yearly rotation of the gdb/ChangeLog file
* [PATCH 2/5] Update copyright year in version message of GDB,
* [PATCH 3/5] gdb/copyright.py: Do not forget to remind about
* [PATCH 4/5] gdb/copyright.py: Remove
* [PATCH 5/5] Update copyright year range in all GDB files
Tested by rebuilding GDB from scratch on x86_64-linux.
Thanks,
--
Joel
next reply other threads:[~2018-01-01 4:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 4:48 Joel Brobecker [this message]
2018-01-01 4:48 ` [PATCH 4/5] gdb/copyright.py: Remove testsuite/gdb.base/step-line.{c,inp} special handling Joel Brobecker
2018-01-01 4:48 ` [PATCH 3/5] gdb/copyright.py: Do not forget to remind about MULTIPLE_COPYRIGHT_HEADERS Joel Brobecker
2018-01-01 4:48 ` [PATCH 2/5] Update copyright year in version message of GDB, GDBserver and GDBreplay Joel Brobecker
2018-01-01 6:09 ` GDB "Start of New Year Procedure" -- 2018 edition Joel Brobecker
2018-01-02 6:13 ` Sergio Durigan Junior
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=20180101044801.7201-1-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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).