From: Eli Zaretskii <eliz@gnu.org>
To: Christian Biesinger <cbiesinger@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4] [PR/24474] Add gdb.lookup_static_symbol to the python API
Date: Tue, 30 Jul 2019 15:57:00 -0000 [thread overview]
Message-ID: <83r267ikgf.fsf@gnu.org> (raw)
In-Reply-To: <CAPTJ0XGOTbb3Cear=hF8pxaC0b-PxkSOMK1DTPs0nrfckjaMPg@mail.gmail.com> (message from Christian Biesinger on Tue, 30 Jul 2019 10:40:22 -0500)
> From: Christian Biesinger <cbiesinger@google.com>
> Date: Tue, 30 Jul 2019 10:40:22 -0500
>
> Hi Eli,
>
> could you take a look at the documentation parts of the below patch
> before I push? Thanks!
Didn't I just approve it? Or maybe I got confused by the many
versions of similar patches?
Anyway, this is OK.
next prev parent reply other threads:[~2019-07-30 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 1:24 [PATCH][PR/24474] Make gdb.lookup_static_symbol also check the STATIC_SCOPE Christian Biesinger via gdb-patches
2019-06-18 20:15 ` Christian Biesinger via gdb-patches
2019-07-08 22:05 ` [PING] " Christian Biesinger via gdb-patches
2019-07-15 16:52 ` Christian Biesinger via gdb-patches
2019-07-16 3:28 ` Simon Marchi
2019-07-26 22:05 ` Christian Biesinger via gdb-patches
2019-07-26 22:23 ` [PATCH v2] [PR/24474] Add gdb.lookup_static_symbol to the python API Christian Biesinger via gdb-patches
2019-07-30 1:14 ` Simon Marchi
2019-07-30 1:35 ` [PATCH v3] " Christian Biesinger via gdb-patches
2019-07-30 1:50 ` Simon Marchi
2019-07-30 1:59 ` [PATCH v4] " Christian Biesinger via gdb-patches
2019-07-30 15:41 ` Christian Biesinger via gdb-patches
2019-07-30 15:57 ` Eli Zaretskii [this message]
2019-07-30 16:01 ` Christian Biesinger via gdb-patches
2019-07-26 22:43 ` [PATCH][PR/24474] Make gdb.lookup_static_symbol also check the STATIC_SCOPE Simon Marchi
2019-08-01 19:05 ` Christian Biesinger via gdb-patches
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=83r267ikgf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cbiesinger@google.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