From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Make the windows-nat.c target inherit inf-child.c.
Date: Wed, 12 Mar 2014 11:29:00 -0000 [thread overview]
Message-ID: <532044FA.7060704@redhat.com> (raw)
In-Reply-To: <20140312090656.GF4882@adacore.com>
On 03/12/2014 09:06 AM, Joel Brobecker wrote:
> Hi Pedro,
>
>> I wonder whether anyone with easier Windows than me wants
>> to run this through the test suite? Otherwise, with the
>> little Wine test I did, I'm pretty sure I didn't break
>> things too much. :-)
>
> I ran this patch against our testsuite on Windows, and found
> no regression. I think it's good :-)...
Thank you! This series is now all in.
--
Pedro Alves
next prev parent reply other threads:[~2014-03-12 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 15:14 [PATCH 0/3] Make all native targets " Pedro Alves
2014-03-07 15:14 ` [PATCH 2/3] Make the windows-nat.c target " Pedro Alves
2014-03-11 16:42 ` Pedro Alves
2014-03-12 9:07 ` Joel Brobecker
2014-03-12 11:29 ` Pedro Alves [this message]
2014-03-07 15:15 ` [PATCH 3/3] Make the nto-procfs.c " Pedro Alves
2014-03-07 15:15 ` [PATCH 1/3] Make the go32-nat.c " Pedro Alves
2014-03-07 15:32 ` Eli Zaretskii
2014-03-07 15:38 ` Pedro Alves
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=532044FA.7060704@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.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