From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb: update some copyright years (2022 -> 2023)
Date: Wed, 01 Mar 2023 18:36:53 -0700 [thread overview]
Message-ID: <871qm8lyru.fsf@tromey.com> (raw)
In-Reply-To: <20230301200940.899631-1-simon.marchi@efficios.com> (Simon Marchi via Gdb-patches's message of "Wed, 1 Mar 2023 15:09:40 -0500")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> The copyright years in the ROCm files (e.g. solib-rocm.c) are wrong,
Simon> they end in 2022 instead of 2023. I suppose because I posted (or at
Simon> least prepared) the patches in 2022 but merged them in 2023, and forgot
Simon> to update the year.
I think I've done this myself :)
Simon> I found a bunch of other files that are in the same
Simon> situation. Fix them all up.
Simon> gdb/python/lib/gdb/dap/__init__.py | 2 +-
Oh, look.
Anyway, thank you, looks good to me.
Tom
next prev parent reply other threads:[~2023-03-02 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 20:09 Simon Marchi
2023-03-02 1:36 ` Tom Tromey [this message]
2023-03-02 1:55 ` 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=871qm8lyru.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).