From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: FYI: Updating Copyright Year ranges for GDB to add year 2023
Date: Sun, 1 Jan 2023 16:57:10 +0400 [thread overview]
Message-ID: <20230101125854.2204219-1-brobecker@adacore.com> (raw)
Happy New Year :).
For the record, I'm about to apply the following patches to update
the copyright year ranges of the GDB sources to add year 2023.
The copyright.py script detected a problem, which was due to
a file rename, so I adjusted the script accordingly (patch #2).
I will push the following patches now:
* [PATCH 1/4] Update copyright year in help message of gdb, gdbserver,
* [PATCH 2/4] gdb/copyright.py: Adjust following rename of
* [PATCH 3/4] Update copyright year range in header of all files
* [PATCH 4/4] manual copyright year range of various GDB files to add
Thank you,
--
Joel
next reply other threads:[~2023-01-01 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 12:57 Joel Brobecker [this message]
2023-01-01 12:57 ` [PATCH 1/4] Update copyright year in help message of gdb, gdbserver, gdbreplay Joel Brobecker
2023-01-01 12:57 ` [PATCH 2/4] gdb/copyright.py: Adjust following rename of sim/ppc/ppc-instructions Joel Brobecker
2023-01-01 12:57 ` [PATCH 3/4] Update copyright year range in header of all files managed by GDB Joel Brobecker
2023-01-01 13:04 ` Joel Brobecker
2023-01-01 12:57 ` [PATCH 4/4] manual copyright year range of various GDB files to add 2023 Joel Brobecker
2023-01-01 13:17 ` FYI: Updating Copyright Year ranges for GDB to add year 2023 Joel Brobecker
2023-01-04 16:06 ` Simon Marchi
2023-01-06 2:59 ` Joel Brobecker
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=20230101125854.2204219-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).