Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PING] [PATCH 0/4] [pre-commit] Add copyright-years check
Date: Mon, 1 Jun 2026 15:10:25 +0200	[thread overview]
Message-ID: <b84c4f83-dcbc-43f8-9647-81c1138c766b@suse.de> (raw)
In-Reply-To: <20260429081337.1563201-1-tdevries@suse.de>

On 4/29/26 10:13 AM, Tom de Vries wrote:
> I ran gdb/copyright.py, and found two files with incorrect copyright
> years [1].
> 
> I decided to use the script in a pre-commit check, to detect this sort of
> thing automatically.
> 

Ping.

Thanks,
- Tom

> [1] https://sourceware.org/pipermail/gdb-patches/2026-April/226916.html
> 
> Tom de Vries (4):
>    [gdb] Handle empty list in update_files in copyright.py
>    [gdb] Factor out filter_excluded out of update_files in copyright.py
>    [gdb] Require python >= 3.13 in copyright.py
>    [pre-commit] Add copyright-years check
> 
>   .pre-commit-config.yaml |  7 ++++++
>   gdb/copyright.py        | 54 +++++++++++++++++++++++++++++------------
>   2 files changed, 46 insertions(+), 15 deletions(-)
> 
> 
> base-commit: 8a5e138e6276ce7644ab858751440cb59f35623b


      parent reply	other threads:[~2026-06-01 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  8:13 Tom de Vries
2026-04-29  8:13 ` [PATCH 1/4] [gdb] Handle empty list in update_files in copyright.py Tom de Vries
2026-04-29  8:13 ` [PATCH 2/4] [gdb] Factor out filter_excluded out of " Tom de Vries
2026-04-29  8:13 ` [PATCH 3/4] [gdb] Require python >= 3.13 " Tom de Vries
2026-04-29  8:13 ` [PATCH 4/4] [pre-commit] Add copyright-years check Tom de Vries
2026-06-01 13:23   ` Tom de Vries
2026-06-01 13:10 ` Tom de Vries [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=b84c4f83-dcbc-43f8-9647-81c1138c766b@suse.de \
    --to=tdevries@suse.de \
    --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