From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] [gdb/testsuite] Codespell fixes
Date: Wed, 10 Jun 2026 11:42:16 +0200 [thread overview]
Message-ID: <7a49de4a-d67e-4942-aef1-40fb5713500c@suse.de> (raw)
In-Reply-To: <20260608171304.3986416-3-tdevries@suse.de>
On 6/8/26 7:12 PM, Tom de Vries wrote:
> Fix typos in gdb/testsuite using an interactive session:
> ...
> $ codespell --toml gdb/pyproject.toml -w -i 3 gdb/testsuite
> ...
I've reviewed this using Claude Code.
It had some "minor observations" about:
- variable name change in gdb.threads/fork-plus-threads.c,
- changing "crasher" to "crash" (asserting that "crasher"
is valid developer jargon)
but no real objections.
I'm pushing this.
Thanks,
- Tom
prev parent reply other threads:[~2026-06-10 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 17:12 [PATCH 0/2] " Tom de Vries
2026-06-08 17:12 ` [PATCH 1/2] [gdb/testsuite] Fix typo in configure.ac Tom de Vries
2026-06-09 17:08 ` Tom Tromey
2026-06-08 17:12 ` [PATCH 2/2] [gdb/testsuite] Codespell fixes Tom de Vries
2026-06-10 9:42 ` 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=7a49de4a-d67e-4942-aef1-40fb5713500c@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