From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PING^2][PATCH 0/7] [pre-commit] Some codespell fixes
Date: Mon, 1 Jun 2026 14:34:47 +0200 [thread overview]
Message-ID: <07f923a9-8fcd-4599-92d7-cd9fd8f88ebe@suse.de> (raw)
In-Reply-To: <59458a76-e075-444d-b361-8aaf22783eb5@suse.de>
On 4/24/26 3:20 PM, Tom de Vries wrote:
> On 4/10/26 2:38 PM, Tom de Vries wrote:
>> On 3/10/26 10:18 AM, Tom de Vries wrote:
>>> This series contains some codespell fixes.
>>>
>>> The first patch fixes the codespell:ignore-begin/end to be non-greedy.
>>>
>>> The second patch gets rid of gdb/contrib/setup.cfg.
>>>
>>> The rest of the patches each make one gdb subdir codespell-clean.
>>>
>
>
> Ping^2.
>
I've asked Claude Code to review this patch series.
It found a problem in the second patch: it added an empty pyproject.toml.
I've removed this, and pushed the series.
Thanks,
- Tom
> Thanks,
> - Tom
>
>>> Tom de Vries (7):
>>> [pre-commit] Make codespell:ignore-begin/end non-greedy
>>> [pre-commit] Move gdb/contrib/setup.cfg to gdb/pyproject.toml
>>> [pre-commit] Make gdb/contrib codespell-clean
>>> [pre-commit] Make gdb/nat codespell-clean
>>> [pre-commit] Make gdb/features codespell-clean
>>> [pre-commit] Make gdb/stubs codespell-clean
>>> [pre-commit] Make gdb/doc codespell-clean
>>>
>>> .pre-commit-config.yaml | 6 +--
>>> gdb/contrib/ari/update-web-ari.sh | 4 +-
>>> gdb/contrib/codespell-ignore-words.txt | 6 ++-
>>> gdb/contrib/dwarf-to-dwarf-assembler.py | 2 +-
>>> gdb/contrib/setup.cfg | 13 ------
>>> gdb/doc/gdb.texinfo | 58 ++++++++++++++++++-------
>>> gdb/features/alpha-core.xml | 2 +
>>> gdb/features/arc/v2-core.xml | 2 +-
>>> gdb/features/i386/32bit-sse.xml | 2 +
>>> gdb/features/i386/64bit-sse.xml | 2 +
>>> gdb/features/or1k-core.xml | 2 +
>>> gdb/features/rs6000/powerpc-602.xml | 2 +
>>> gdb/features/rx.xml | 2 +
>>> gdb/nat/linux-btrace.c | 2 +-
>>> gdb/pyproject.toml | 14 ++++++
>>> gdb/stubs/i386-stub.c | 2 +-
>>> gdb/stubs/ia64vms-stub.c | 4 +-
>>> gdb/stubs/m32r-stub.c | 4 +-
>>> gdb/stubs/m68k-stub.c | 4 +-
>>> gdb/stubs/sh-stub.c | 2 +-
>>> gdb/stubs/sparc-stub.c | 2 +-
>>> gdb/stubs/z80-stub.c | 9 ++--
>>> pyproject.toml | 0
>>> 23 files changed, 95 insertions(+), 51 deletions(-)
>>> delete mode 100644 gdb/contrib/setup.cfg
>>> create mode 100644 pyproject.toml
>>>
>>>
>>> base-commit: 55c46eed2c8a132df2cd98cd0115ad6862604ca2
>>
>
prev parent reply other threads:[~2026-06-01 12:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 9:18 [PATCH " Tom de Vries
2026-03-10 9:18 ` [PATCH 1/7] [pre-commit] Make codespell:ignore-begin/end non-greedy Tom de Vries
2026-03-10 9:18 ` [PATCH 2/7] [pre-commit] Move gdb/contrib/setup.cfg to gdb/pyproject.toml Tom de Vries
2026-03-10 9:18 ` [PATCH 3/7] [pre-commit] Make gdb/contrib codespell-clean Tom de Vries
2026-03-10 9:18 ` [PATCH 4/7] [pre-commit] Make gdb/nat codespell-clean Tom de Vries
2026-03-10 9:18 ` [PATCH 5/7] [pre-commit] Make gdb/features codespell-clean Tom de Vries
2026-03-10 9:18 ` [PATCH 6/7] [pre-commit] Make gdb/stubs codespell-clean Tom de Vries
2026-03-10 9:18 ` [PATCH 7/7] [pre-commit] Make gdb/doc codespell-clean Tom de Vries
2026-03-24 15:37 ` [PING][PATCH 0/7] [pre-commit] Some codespell fixes Tom de Vries
2026-04-10 12:38 ` Tom de Vries
2026-04-24 13:20 ` [PING^2][PATCH " Tom de Vries
2026-06-01 12:34 ` 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=07f923a9-8fcd-4599-92d7-cd9fd8f88ebe@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