From: Tom de Vries <tdevries@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] [gdb] Fix some typos
Date: Wed, 9 Sep 2026 13:49:03 +0200 [thread overview]
Message-ID: <52bc3c42-47ff-400e-a0ab-0bca209dede6@suse.de> (raw)
In-Reply-To: <86y0dg242d.fsf@gnu.org>
On 9/4/26 9:45 PM, Eli Zaretskii wrote:
>> From: Tom de Vries <tdevries@suse.de>
>> Date: Fri, 4 Sep 2026 19:39:33 +0200
>>
>> Detect typos in words containing dashes by enabling the regex field in the
>> codespell configuration in pyproject, and dropping the dash.
>>
>> Fix some typos manually (not using codespell -w).
>>
>> This also triggers codespell to work on the rules in
>> gdb/contrib/codespell-dictionary.txt, so skip it.
>
> Typo fixes fall under the "obvious fix" rule, and don't need any
> approvals.
>
Hi Eli,
True.
I was mostly interested in review of the first patch, and the commit
message of this patch references the first patch, so I submitted it as a
series rather than just applying it.
Anyway, I've pushed this series.
Thanks,
- Tom
> Thanks.
prev parent reply other threads:[~2026-09-09 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 17:39 [PATCH 1/2] [gdb] Document word regexp choice in pyproject.toml Tom de Vries
2026-09-04 17:39 ` [PATCH 2/2] [gdb] Fix some typos Tom de Vries
2026-09-04 19:45 ` Eli Zaretskii
2026-09-09 11:49 ` 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=52bc3c42-47ff-400e-a0ab-0bca209dede6@suse.de \
--to=tdevries@suse.de \
--cc=eliz@gnu.org \
--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