From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [pre-commit] Add tclint hook
Date: Wed, 17 Sep 2025 09:42:30 -0600 [thread overview]
Message-ID: <87frcljdax.fsf@tromey.com> (raw)
In-Reply-To: <20250915084105.23171-1-tdevries@suse.de> (Tom de Vries's message of "Mon, 15 Sep 2025 10:41:05 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> Add a pre-commit hook that enables tclint [1] (a Tcl linter) for the gdb
Tom> testsuite.
Tom> The pre-commit hook doesn't reference the official url, because that one
Tom> doesn't have pre-commit support yet [2].
My first reaction was to say we should wait but after reflecting a bit,
I think it's probably better to just go ahead and then switch when
tclint upstream catches up.
Tom> Also add a tclint configuration file gdb/testsuite/tclint.toml.
How about using pyproject.toml so we can have (nearly) all this kind of
config in one spot?
Tom
next prev parent reply other threads:[~2025-09-17 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 8:41 Tom de Vries
2025-09-17 15:42 ` Tom Tromey [this message]
2025-09-17 18:15 ` Tom de Vries
2025-09-17 18:35 ` Tom Tromey
2025-09-17 19:08 ` Tom de Vries
2025-09-17 19:43 ` Tom de Vries
2025-09-18 0:22 ` Tom Tromey
2025-09-19 7:14 ` 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=87frcljdax.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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