From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>, Simon Marchi <simark@simark.ca>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix Value.format_string docu for static members argument
Date: Sun, 29 Nov 2020 18:16:26 +0000 (UTC) [thread overview]
Message-ID: <1389746267.5076756.1606673786029@mail.yahoo.com> (raw)
In-Reply-To: <9f571454-1cdf-1af5-edb0-2f7732a88942@simark.ca>
Am Dienstag, 24. November 2020, 20:18:14 MEZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:
> On 2020-11-24 2:15 p.m., Hannes Domani via Gdb-patches wrote:
> > Am Dienstag, 24. November 2020, 20:13:25 MEZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:
> >
> >> On 2020-11-24 2:10 p.m., Eli Zaretskii via Gdb-patches wrote:
> >>
> >>>> Date: Tue, 24 Nov 2020 19:49:38 +0100
> >>>> From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
> >>>>
> >>>> The argument is called static_members, not static_fields.
> >>>>
> >>>> gdb/doc/ChangeLog:
> >>>>
> >>>> 2020-11-24 Hannes Domani <ssbssa@yahoo.de>
> >>>>
> >>>> * python.texi: Fix docu for static members argument.
> >>>
> >>> OK, thanks.
> >>
> >>>
> >>
> >> It wouldn't hurt to push this patch to the GDB 10 branch, I think.
> >
> > So would this need a PR then?
>
> Hmm, right. Well, if you don't mind creating one it would be nice, but
> otherwise it's not the end of the world.
I've create PR python/26974, and pushed this to master and gdb 10, thanks.
Hannes
prev parent reply other threads:[~2020-11-29 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201124184938.47048-1-ssbssa.ref@yahoo.de>
2020-11-24 18:49 ` Hannes Domani via Gdb-patches
2020-11-24 19:10 ` Eli Zaretskii via Gdb-patches
2020-11-24 19:13 ` Simon Marchi
2020-11-24 19:15 ` Hannes Domani via Gdb-patches
2020-11-24 19:18 ` Simon Marchi
2020-11-29 18:16 ` Hannes Domani via Gdb-patches [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=1389746267.5076756.1606673786029@mail.yahoo.com \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=simark@simark.ca \
--cc=ssbssa@yahoo.de \
/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