From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb, gdbserver: update copyright years in copyright notices
Date: Wed, 30 Jul 2025 13:38:03 -0600 [thread overview]
Message-ID: <87bjp1sc4k.fsf@tromey.com> (raw)
In-Reply-To: <20250725163151.354633-1-simon.marchi@efficios.com> (Simon Marchi's message of "Fri, 25 Jul 2025 12:31:44 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
Simon> The copyright notices printed by these programs still use year 2024.
Simon> Update to 2025.
Simon> It seems like a trivial patch to me, but I am posting it for review, in
Simon> case there's something wrong in the new-year process that caused them to
Simon> be missed, in which case we should address that too.
I just ran the script, I didn't realize there was a documented
procedure.
I wonder if the script could instead be changed to do this, so the
procedure could literally be to run the script.
Tom
next prev parent reply other threads:[~2025-07-30 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 16:31 Simon Marchi
2025-07-25 19:26 ` Kevin Buettner
2025-07-30 19:38 ` Tom Tromey [this message]
2025-08-14 19:23 ` Simon Marchi
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=87bjp1sc4k.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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