From: Matthieu Longo via Gdb <gdb@sourceware.org>
To: Tom Tromey <tom@tromey.com>, Matthieu Longo via Gdb <gdb@sourceware.org>
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: RFC: prototype of C extensions using the Python limited API
Date: Mon, 29 Jun 2026 11:37:00 +0100 [thread overview]
Message-ID: <c65aa541-16b1-4424-a10c-131b42b170d9@arm.com> (raw)
In-Reply-To: <f108eac4-ab90-41e5-9c2c-d6d07b217105@arm.com>
On 22/06/2026 10:26, Matthieu Longo via Gdb wrote:
> On 18/06/2026 21:46, Tom Tromey wrote:
>> Matthieu> I don't expect a thorough review of all the code, but a
>> Matthieu> validation of the approach.
>>
>> I'll try to send more next week.
>>
>> Tom
>
> Matthieu
Hi Tom,
First of all, I want to be clear with you that this email is not supposed to make pressure on you
under any circumstances. Thanks for all your time you have been spending reviewing this Python
migration work.
Since we are approaching the summer holidays period, I assume that you must be off for some weeks.
On my side, I plan to be off around the first half of August.
Please could you let me know roughly if this work will be able to progress during the next two
months, or should it wait until later to get more focus ?
Regards,
Matthieu
next prev parent reply other threads:[~2026-06-29 10:38 UTC|newest]
Thread overview: 10+ 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 [this message]
2026-06-22 10:24 ` Matthieu Longo via Gdb
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=c65aa541-16b1-4424-a10c-131b42b170d9@arm.com \
--to=gdb@sourceware.org \
--cc=aburgess@redhat.com \
--cc=matthieu.longo@arm.com \
--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