From: Siva Chandra <sivachandra@google.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] - Exposing find_pc_line through Python API
Date: Sun, 13 May 2012 11:37:00 -0000 [thread overview]
Message-ID: <CAGyQ6gwGKhX3tGPr8j93J7XJvtRfwe9JvLvZK5k+yPBhJXSQLg@mail.gmail.com> (raw)
In-Reply-To: <CADPb22SQ4zQ2vP+2kTSXT8FMaENZbuNTDNKmEhhpfiGA7ofRjg@mail.gmail.com>
On Fri, May 11, 2012 at 11:43 PM, Doug Evans <dje@google.com> wrote:
> Thanks.
> The patch is ok with me.
Now committed.
Thanks,
Siva Chandra
prev parent reply other threads:[~2012-05-13 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 18:11 Siva Chandra
2012-05-07 19:36 ` Eli Zaretskii
2012-05-08 2:35 ` Siva Chandra
2012-05-09 7:35 ` Siva Chandra
2012-05-09 20:05 ` Eli Zaretskii
2012-05-10 21:16 ` Doug Evans
2012-05-11 16:35 ` Siva Chandra
2012-05-11 18:14 ` Doug Evans
2012-05-13 11:37 ` Siva Chandra [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=CAGyQ6gwGKhX3tGPr8j93J7XJvtRfwe9JvLvZK5k+yPBhJXSQLg@mail.gmail.com \
--to=sivachandra@google.com \
--cc=dje@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