From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Use Python safety API in py-symbol.c
Date: Thu, 13 Aug 2026 14:42:17 -0600 [thread overview]
Message-ID: <87wltt7nx2.fsf@tromey.com> (raw)
In-Reply-To: <997f9830-eeb3-4339-895d-38ba74d3fe45@simark.ca> (Simon Marchi's message of "Thu, 13 Aug 2026 10:43:11 -0400")
Simon> Do we need a NEWS entry for the `frame` keyword argument, or it's too
Simon> minor?
Eventually what I think we should do is update the documentation to
reflect the new convention. However we shouldn't do that until the
other varargs calls are switched over.
Tom
prev parent reply other threads:[~2026-08-13 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 0:25 Tom Tromey
2026-08-13 14:43 ` Simon Marchi
2026-08-13 20:42 ` 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=87wltt7nx2.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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