From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Convert py-connection.c to the Python safety API
Date: Wed, 14 Oct 2026 17:55:32 -0600 [thread overview]
Message-ID: <87jynjhm6j.fsf@tromey.com> (raw)
In-Reply-To: <20260904180714.2872376-1-tom@tromey.com> (Tom Tromey's message of "Fri, 4 Sep 2026 12:07:14 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> This changes much of py-connection.c to the Python safety API.
[...]
I'm checking this in. I've made the small changes suggested by Jan in a
response.
Tom
prev parent reply other threads:[~2026-10-14 23:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 18:07 Tom Tromey
2026-09-21 13:29 ` Jan Vrany
2026-09-22 21:16 ` Tom Tromey
2026-10-14 23:55 ` Tom Tromey [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=87jynjhm6j.fsf@tromey.com \
--to=tom@tromey.com \
--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