From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH v2 0/3] Improvements to Python parameters
Date: Wed, 26 Jan 2022 07:06:11 -0700 [thread overview]
Message-ID: <878rv2bnho.fsf@tromey.com> (raw)
In-Reply-To: <20220110215144.1714909-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Mon, 10 Jan 2022 14:51:41 -0700")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> Here's v2 of the series to improve Python parameters in a few ways.
Tom> v1 is here:
Tom> https://sourceware.org/pipermail/gdb-patches/2022-January/184826.html
Tom> I think this fixes all the review comments.
I'm checking this in now.
Tom
prev parent reply other threads:[~2022-01-26 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 21:51 Tom Tromey
2022-01-10 21:51 ` [PATCH v2 1/3] Change how Python architecture and language are handled Tom Tromey
2022-01-31 13:20 ` Simon Marchi
2022-01-10 21:51 ` [PATCH v2 2/3] Fix another crash with gdb parameters in Python Tom Tromey
2022-01-10 21:51 ` [PATCH v2 3/3] Add a way to temporarily set a gdb parameter from Python Tom Tromey
2022-01-13 8:50 ` Lancelot SIX
2022-01-13 19:46 ` Tom Tromey
2022-01-26 14:06 ` 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=878rv2bnho.fsf@tromey.com \
--to=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).