From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: fix a few typos
Date: Mon, 1 Dec 2025 12:16:03 -0500 [thread overview]
Message-ID: <97d882dc-025c-4bce-90e4-8fdeb805390d@polymtl.ca> (raw)
In-Reply-To: <7ead3569-5727-4f12-a9eb-40acf3193c3a@suse.de>
On 2025-12-01 12:12, Tom de Vries wrote:
> Interesting.
>
> I wonder if that will still work with my proposal for moving the
> commit-log check from the commit-msg to the post-commit stage (
> https://sourceware.org/pipermail/gdb-patches/2025-December/223036.html
> ), in which case the commit message is produced by a wrapper script,
> and not by git as is the case for the commit-msg stage.
Depends, what do you mean by "will still work"?
> Also I wonder, don't you get warnings for removed lines in the
> scenario you describe?
I don't recall, but it's possible that I get them and ignore them.
Simon
next prev parent reply other threads:[~2025-12-01 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 21:54 simon.marchi
2025-11-28 10:19 ` Tom de Vries
2025-11-28 15:40 ` Simon Marchi
2025-12-01 17:12 ` Tom de Vries
2025-12-01 17:16 ` Simon Marchi [this message]
2025-12-01 17:27 ` Tom de Vries
2025-12-01 17:37 ` Simon Marchi
2025-12-02 8:07 ` 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=97d882dc-025c-4bce-90e4-8fdeb805390d@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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