From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PR Python/12212
Date: Tue, 23 Nov 2010 13:35:00 -0000 [thread overview]
Message-ID: <m3k4k4i2mt.fsf@redhat.com> (raw)
In-Reply-To: <m3mxp9ez70.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 16 Nov 2010 14:27:47 -0700")
Tom Tromey <tromey@redhat.com> writes:
>>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
>
> Phil> I adjusted the regression test in the previous patch I sent to account
> Phil> for this.
>
> Thanks. This is ok.
>
> Tom
So committed, thanks.
Cheers,
Phil
prev parent reply other threads:[~2010-11-23 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 10:51 Phil Muldoon
2010-11-16 18:40 ` Tom Tromey
2010-11-16 17:47 ` Phil Muldoon
2010-11-16 19:01 ` Tom Tromey
2010-11-16 20:17 ` Phil Muldoon
2010-11-16 21:27 ` Tom Tromey
2010-11-23 13:35 ` Phil Muldoon [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=m3k4k4i2mt.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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