From: Tom Tromey <tom@tromey.com>
To: Matthieu Longo <matthieu.longo@arm.com>
Cc: Tom Tromey <tom@tromey.com>,
gdb@sourceware.org, Andrew Burgess <aburgess@redhat.com>,
Tom de Vries <tdevries@suse.de>
Subject: Re: RFC: prototype of C extensions using the Python limited API
Date: Sat, 22 Aug 2026 15:58:48 -0600 [thread overview]
Message-ID: <87ld9x7r6v.fsf@tromey.com> (raw)
In-Reply-To: <f4b4074b-c547-4948-ae47-86ccb0e722d6@arm.com> (Matthieu Longo's message of "Thu, 20 Aug 2026 14:59:07 +0100")
Matthieu> However, those patches have created a significant amount of
Matthieu> conflicts on my development branch. And since I haven't heard
Matthieu> of you for a while regarding this prototype, should I
Matthieu> understand that you would prefer to prioritize the migration
Matthieu> to the safe API before the migration to the limited API ?
Sorry about that. I personally don't mind holding my patches if that
makes things easier for you, I can rebase them over whatever.
Matthieu> Also, do you think that it would be helpful to discuss over a
Matthieu> zoom call the status of the limited API migration, the
Matthieu> prototype, and what is remaining to be done ?
We could if you think it would help. I've been pretty behind on gdb
lately due to other work stuff, which is the main reason I didn't get
back to you on your proposal. I'll try to read it soon.
Tom
next prev parent reply other threads:[~2026-08-22 21:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 16:24 Matthieu Longo via Gdb
2026-05-28 16:31 ` Matthieu Longo via Gdb
2026-06-01 10:10 ` Matthieu Longo via Gdb
2026-06-08 13:38 ` Matthieu Longo via Gdb
2026-06-10 16:10 ` Andrew Burgess via Gdb
2026-06-16 17:15 ` Matthieu Longo via Gdb
2026-06-18 20:46 ` Tom Tromey
2026-06-22 9:26 ` Matthieu Longo via Gdb
2026-06-29 10:37 ` Matthieu Longo via Gdb
2026-06-22 10:24 ` Matthieu Longo via Gdb
2026-08-20 13:59 ` Matthieu Longo via Gdb
2026-08-22 21:58 ` Tom Tromey [this message]
2026-09-04 16:01 ` Tom Tromey
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=87ld9x7r6v.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb@sourceware.org \
--cc=matthieu.longo@arm.com \
--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