From: Phil Muldoon <pmuldoon@redhat.com>
To: Matt Rice <ratmice@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [python] find_line_pc_range
Date: Tue, 05 Jul 2011 20:41:00 -0000 [thread overview]
Message-ID: <m3iprgqxi0.fsf@redhat.com> (raw)
In-Reply-To: <CACTLOFremXGUmj6Gk=EHtmtP5HYdVZM_f8f=oeJJrWQgho+6zA@mail.gmail.com> (Matt Rice's message of "Mon, 4 Jul 2011 19:25:51 -0700")
Matt Rice <ratmice@gmail.com> writes:
>>> Thanks, attached is an updated patch that also includes tests.
Matt
This looks ok by me. A maintainer will still have to look over it and
ACK it.
Cheers,
Phil
next prev parent reply other threads:[~2011-07-05 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 4:03 Matt Rice
2011-07-03 16:35 ` Phil Muldoon
2011-07-04 5:38 ` Phil Muldoon
2011-07-04 6:36 ` Matt Rice
2011-07-04 10:09 ` Phil Muldoon
2011-07-05 2:47 ` Matt Rice
2011-07-05 20:41 ` Phil Muldoon [this message]
2011-07-04 10:50 ` Eli Zaretskii
2011-07-04 10:56 ` Matt Rice
2011-07-04 13:14 ` Eli Zaretskii
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=m3iprgqxi0.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ratmice@gmail.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