From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/5] [pre-commit] Some pre-commit improvements
Date: Tue, 25 Aug 2026 14:52:23 +0200 [thread overview]
Message-ID: <9e75aade-2be3-4cf0-9fa8-7650ce3b9085@suse.de> (raw)
In-Reply-To: <13e7e583-9314-4c8e-b599-ee9f6a502eae@suse.de>
On 8/13/26 7:26 AM, Tom de Vries wrote:
> On 8/12/26 8:16 PM, Simon Marchi wrote:
>> On 7/20/26 8:50 AM, Tom de Vries wrote:
>>> This patch series contains some pre-commit improvements.
>>>
>>> The third patch fixes the problem that flake8 is not run for gdb/gdb-
>>> gdb.py.in.
>>>
>>> The first and second patch fix flake8 problems in gdb/gdb-gdb.py.in.
>>>
>>> The fourth and fifth patch makes pre-commit rely less on types
>>> filtering,
>>> fixing PR build/34411.
>>>
>>> Tested on x86_64-linux.
>>>
>>> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34411
>>>
>>> Tom de Vries (5):
>>> [gdb] Fix bare except in gdb/gdb-gdb.py.in
>>> [gdb] Remove superfluous global in gdb/gdb-gdb.py.in
>>> [pre-commit] Run flake8 for gdb/gdb-gdb.py.in
>>> [pre-commit] Don't require text type for check-whitespace hook
>>> [pre-commit] Don't require text type for codespell hook
>>
>> FYI, I think that patches 1 and 2 are no longer necessary, because the
>> code has changed.
>
> Indeed, thanks for pointing that out.
>
> I've now submitted an alternative to patch 3.
>
I've now pushed that one.
> Patches 4 and 5 still make sense, but both don't apply cleanly without
> patch 3. So I'll wait what happens with the alternative to decide how
> to proceed.
>
I've updated and pushed these two as well.
Thanks,
- Tom
prev parent reply other threads:[~2026-08-25 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 12:50 Tom de Vries
2026-07-20 12:50 ` [PATCH 1/5] [gdb] Fix bare except in gdb/gdb-gdb.py.in Tom de Vries
2026-07-20 12:50 ` [PATCH 2/5] [gdb] Remove superfluous global " Tom de Vries
2026-07-20 12:50 ` [PATCH 3/5] [pre-commit] Run flake8 for gdb/gdb-gdb.py.in Tom de Vries
2026-08-12 18:15 ` Simon Marchi
2026-08-13 5:19 ` Tom de Vries
2026-07-20 12:50 ` [PATCH 4/5] [pre-commit] Don't require text type for check-whitespace hook Tom de Vries
2026-07-20 12:50 ` [PATCH 5/5] [pre-commit] Don't require text type for codespell hook Tom de Vries
2026-08-03 12:25 ` [PING][PATCH 0/5] [pre-commit] Some pre-commit improvements Tom de Vries
2026-08-12 18:16 ` [PATCH " Simon Marchi
2026-08-13 5:26 ` Tom de Vries
2026-08-25 12:52 ` 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=9e75aade-2be3-4cf0-9fa8-7650ce3b9085@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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