From: "Kévin Le Gouguec" <legouguec@adacore.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Simon Marchi <simark@simark.ca>, Tom Tromey <tom@tromey.com>,
Tom Tromey <tromey@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Add flake8 and isort to .pre-commit-config.yaml
Date: Tue, 09 Apr 2024 15:04:28 +0200 [thread overview]
Message-ID: <87wmp6offn.fsf@adacore.com> (raw)
In-Reply-To: <ec8edb49-8590-4191-b02b-5317b91f2274@suse.de> (Tom de Vries's message of "Tue, 9 Apr 2024 14:56:13 +0200")
Tom de Vries <tdevries@suse.de> writes:
> But when running git commit, the wrong one was used. I just needed to rerun "pre-commit install" to re-install the hooks, which fixes this.
Oooh, hadn't though of that - pre-commit does capture an
"INSTALL_PYTHON" into .git/hooks/pre-commit. Good catch!
next prev parent reply other threads:[~2024-04-09 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 18:11 Tom Tromey
2024-04-02 20:26 ` Simon Marchi
2024-04-03 19:52 ` Tom Tromey
2024-04-03 19:57 ` Simon Marchi
2024-04-09 7:58 ` Tom de Vries
2024-04-09 9:41 ` Kévin Le Gouguec
2024-04-09 12:56 ` Tom de Vries
2024-04-09 13:04 ` Kévin Le Gouguec [this message]
2024-04-09 15:22 ` Tom Tromey
2024-04-10 5:38 ` 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=87wmp6offn.fsf@adacore.com \
--to=legouguec@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tdevries@suse.de \
--cc=tom@tromey.com \
--cc=tromey@adacore.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).