From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 9/9] [pre-commit] Simplify codespell configuration
Date: Mon, 15 Jun 2026 13:16:40 +0200 [thread overview]
Message-ID: <2e77bdde-b982-4f8b-8030-964ac7b19cb6@suse.de> (raw)
In-Reply-To: <20260603100516.144737-10-tdevries@suse.de>
On 6/3/26 12:05 PM, Tom de Vries wrote:
> In order to separate the files we want to skip from the files that are todo,
> I added a marker TODO-SEPARATOR in the list.
I looked again at this, and found that I could simply do:
...
skip = [
# Comment 1
'file1',
'file2',
# Comment 1
'file3',
'file4'
]
...
so I'm pushing this variant.
Thanks,
- Tom
next prev parent reply other threads:[~2026-06-15 11:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 10:05 [PATCH 0/9] [gdb] Make gdb dir codespell-clean Tom de Vries
2026-06-03 10:05 ` [PATCH 1/9] [gdb] Drop executable mode in some files Tom de Vries
2026-06-04 20:05 ` Simon Marchi
2026-06-04 20:07 ` Tom de Vries
2026-06-03 10:05 ` [PATCH 2/9] [gdb/contrib] Describe words in codespell-ignore-words.txt Tom de Vries
2026-06-03 10:05 ` [PATCH 3/9] [gdb/contrib] Extend codespell-ignore-words.txt Tom de Vries
2026-06-03 10:05 ` [PATCH 4/9] [gdb] Fix typos Tom de Vries
2026-06-03 10:05 ` [PATCH 5/9] [gdb] Fix codespell false positives by ignoring Tom de Vries
2026-06-03 10:05 ` [PATCH 6/9] [gdb] Fix codespell false positive by string splitting Tom de Vries
2026-06-03 10:05 ` [PATCH 7/9] [gdb] Fix codespell false positives by renaming Tom de Vries
2026-06-03 10:05 ` [PATCH 8/9] [pre-commit] Include gdb in codespell check Tom de Vries
2026-06-03 10:05 ` [PATCH 9/9] [pre-commit] Simplify codespell configuration Tom de Vries
2026-06-15 11:16 ` Tom de Vries [this message]
2026-06-15 10:29 ` [PATCH 0/9] [gdb] Make gdb dir codespell-clean Tom de Vries
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=2e77bdde-b982-4f8b-8030-964ac7b19cb6@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