Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix copyright dates for new files
Date: Wed, 11 Feb 2026 16:14:43 -0500	[thread overview]
Message-ID: <00604a1d-a3e1-435e-afd6-95a32d2b6c94@simark.ca> (raw)
In-Reply-To: <87cy2baswa.fsf@tromey.com>



On 2026-02-11 16:10, Tom Tromey wrote:
>>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:
> 
> Tom> I forgot to add 2026 to a copyright date in a file I recently
> Tom> committed (but had originally submitted in 2025).  Thinking this might
> Tom> have happened before, I re-ran gdb/copyright.py and it pointed out a
> Tom> surprising number of such changes.
> 
> I found one more of these in a recent patch of mine.
> I'm going to check this all in now.
> 
> Tom

Just an idea, the buildbot could perhaps run gdb/copyright.py and error
out if there is a diff (the same job that runs black and other checks).

Simon

      reply	other threads:[~2026-02-11 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 18:18 Tom Tromey
2026-02-11 21:10 ` Tom Tromey
2026-02-11 21:14   ` Simon Marchi [this message]

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=00604a1d-a3e1-435e-afd6-95a32d2b6c94@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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