From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] [gdb] Add c_ctrl/c_unctrl
Date: Thu, 26 Mar 2026 15:07:37 +0100 [thread overview]
Message-ID: <8f9ffb89-bd76-4808-9e3f-ee24e72a0e36@suse.de> (raw)
In-Reply-To: <62794ee3-ffc9-4bbc-959f-bee3f06947e5@suse.de>
On 3/26/26 10:57 AM, Tom de Vries wrote:
>
> I've pushed the patch, but I may submit a follow-up patch implementing
> (my current understanding of) your suggestion.
I've posted a follow-up patch (
https://sourceware.org/pipermail/gdb-patches/2026-March/226238.html ).
Thanks,
- Tom
prev parent reply other threads:[~2026-03-26 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 12:39 Tom de Vries
2026-03-25 17:40 ` Tom Tromey
2026-03-25 18:12 ` Tom de Vries
2026-03-25 19:45 ` Tom Tromey
2026-03-25 20:50 ` Tom Tromey
2026-03-26 9:57 ` Tom de Vries
2026-03-26 14:07 ` 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=8f9ffb89-bd76-4808-9e3f-ee24e72a0e36@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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