From: Tom Tromey <tromey@redhat.com>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [python] mi/12531
Date: Tue, 19 Apr 2011 13:07:00 -0000 [thread overview]
Message-ID: <m3k4eq5r00.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3k4eqfrgp.fsf@redhat.com> (Phil Muldoon's message of "Tue, 19 Apr 2011 11:47:18 +0100")
>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
Phil> You did not give an explicit ok, so I am attaching the patch. I won't
Phil> attach the ChangeLog again, but I will attach the relevant bz entries.
Ok.
Phil> Also, as this tends to block Dodji's use of pretty-printing in Nemiver, is
Phil> it ok for the 7.3 branch too?
Sure, thanks.
Tom
next prev parent reply other threads:[~2011-04-19 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 14:26 Phil Muldoon
2011-04-18 20:58 ` Tom Tromey
2011-04-19 10:47 ` Phil Muldoon
2011-04-19 13:07 ` Tom Tromey [this message]
2011-04-29 12:52 ` Phil Muldoon
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=m3k4eq5r00.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.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