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: Re: [PATCH 4/4] [pre-commit] Add copyright-years check
Date: Mon, 1 Jun 2026 15:23:43 +0200	[thread overview]
Message-ID: <541889e0-5b09-4a27-bed8-f137fedf6336@suse.de> (raw)
In-Reply-To: <20260429081337.1563201-5-tdevries@suse.de>

On 4/29/26 10:13 AM, Tom de Vries wrote:
> The first time though someone tries to commit something in a new year, this
> check will generate a massive amount of changes. 

I'm starting to think that this is an advantage.  Probably the earlier 
we address updating copyright years, the better, and this check will 
remind some developer to do it.

> [ Note that the script still
> needs running manually, since the pre-commit check uses only part of the
> script. ]
> 
> We could fix this by hardcoding the year, and require manual bumping after all
> the other files are updated, but I left this as is.

Hmm, say we commit this series in 2026, and then in 2027 check out some 
version from 2026 and run pre-commit.  It will try to update to 2027, 
which isn't a good idea.  So maybe using the year from the last commit 
would work better.

Thanks,
- Tom

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  8:13 [PATCH 0/4] " 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 [this message]
2026-06-01 13:10 ` [PING] [PATCH 0/4] " Tom de Vries

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=541889e0-5b09-4a27-bed8-f137fedf6336@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