From: Eli Zaretskii <eliz@gnu.org>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: gdb-patches@sourceware.org, simonsobisch@web.de, tom@tromey.com
Subject: Re: [PATCH v7 1/4] GDB/Python: Use None for `var_zuinteger_unlimited' value set to `unlimited'
Date: Sat, 29 Oct 2022 18:06:34 +0300 [thread overview]
Message-ID: <83wn8ihdol.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.2210290013440.19931@tpp.orcam.me.uk> (macro@embecosm.com)
> Date: Sat, 29 Oct 2022 14:53:18 +0100 (BST)
> From: "Maciej W. Rozycki" <macro@embecosm.com>
> Cc: Simon Sobisch <simonsobisch@web.de>, Tom Tromey <tom@tromey.com>
>
> ---
> gdb/NEWS | 7 +++++++
> gdb/doc/python.texi | 30 +++++++++++++++++++-----------
> gdb/python/python.c | 10 +++++++++-
> gdb/testsuite/gdb.python/py-parameter.exp | 16 +++++-----------
> 4 files changed, 40 insertions(+), 23 deletions(-)
Thanks, the documentation parts are approved.
next prev parent reply other threads:[~2022-10-29 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 13:53 [PATCH v7 0/4] gdb: split array and string limiting options Maciej W. Rozycki
2022-10-29 13:53 ` [PATCH v7 1/4] GDB/Python: Use None for `var_zuinteger_unlimited' value set to `unlimited' Maciej W. Rozycki
2022-10-29 15:06 ` Eli Zaretskii [this message]
2022-10-29 13:53 ` [PATCH v7 2/4] GDB: Allow arbitrary keywords in integer set commands Maciej W. Rozycki
2022-10-29 15:07 ` Eli Zaretskii
2022-10-31 18:48 ` Simon Marchi
2022-10-31 19:22 ` Simon Marchi
2022-11-24 11:38 ` Maciej W. Rozycki
2022-10-29 13:53 ` [PATCH v7 3/4] GDB: Add a character string limiting option Maciej W. Rozycki
2022-10-29 15:11 ` Eli Zaretskii
2022-10-29 13:53 ` [PATCH v7 4/4] GDB/testsuite: Expand for character string limiting options Maciej W. Rozycki
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=83wn8ihdol.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@embecosm.com \
--cc=simonsobisch@web.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).