public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix "set" handling of Python parameters
Date: Wed, 30 May 2018 23:16:00 -0000	[thread overview]
Message-ID: <20180530230854.psniap3tggl34256@adacore.com> (raw)
In-Reply-To: <20180426225140.18640-1-tom@tromey.com>

Hi Tom,

> gdb/ChangeLog
> 2018-04-26  Tom Tromey  <tom@tromey.com>
> 
> 	* NEWS: Mention new "set" behavior.
> 	* python/py-param.c (get_set_value): Don't print an empty string.
> 	Don't call get_doc_string.
> 
> gdb/doc/ChangeLog
> 2018-04-26  Tom Tromey  <tom@tromey.com>
> 
> 	* python.texi (Parameters In Python): Update get_set_string
> 	documentation.

So sorry again for the long delay in getting this patch reviewed.
Looks good!

-- 
Joel

      parent reply	other threads:[~2018-05-30 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 22:51 Tom Tromey
2018-04-27  6:42 ` Eli Zaretskii
2018-04-30 13:01 ` Phil Muldoon
2018-05-25 17:34 ` Tom Tromey
2018-05-30 23:16 ` Joel Brobecker [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=20180530230854.psniap3tggl34256@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --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).