Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] [pre-commit] Add check-new-file-license
Date: Thu, 18 Jun 2026 14:59:29 +0200	[thread overview]
Message-ID: <b2997b56-933c-48a8-8c48-60638ffd6583@suse.de> (raw)
In-Reply-To: <a412eeea-b057-4316-bc23-921e2b303814@suse.de>

On 6/17/26 9:19 PM, Tom de Vries wrote:
>> I didn't know about this file.  Weird that it has a '.sh' extension.
>>
> 
> Yeah.  Renaming it to .py show some pre-commit errors:
> ...
> gdb/contrib/license-check-new-files.py:58:5: E722 do not use bare 'except'
> gdb/contrib/license-check-new-files.py:106:9: E722 do not use bare 'except'
> ...

I've submitted a fix ( 
https://sourceware.org/pipermail/gdb-patches/2026-June/228100.html ).

Thanks,
- Tom

      reply	other threads:[~2026-06-18 12:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05 14:10 Tom de Vries
2026-06-05 18:06 ` Keith Seitz
2026-06-17 17:45 ` Tom Tromey
2026-06-17 19:19   ` Tom de Vries
2026-06-18 12:59     ` 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=b2997b56-933c-48a8-8c48-60638ffd6583@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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