From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] windows-nat.c: Don't install a deprecated_xfer_memory method.
Date: Tue, 27 Aug 2013 11:38:00 -0000 [thread overview]
Message-ID: <521C8FB1.4000601@redhat.com> (raw)
In-Reply-To: <20130823200850.GF5221@adacore.com>
On 08/23/2013 09:08 PM, Joel Brobecker wrote:
>> I'm not setup for proper Cygwin/Windows testing, but I managed to
>> cross build gdb from GNU/Linux, and copy the resulting binary to a
>> Windows box. Running that gdb on itself worked well enough to run to
>> main, so I can't imagine any regression from this. Does anyone want
>> (and is willing) to run this through the testsuite?
>
> I can give it a spin, but probably not before sometime next week...
Thanks Joel. Yao already ran this through testing, so it
won't be necessary either.
--
Pedro Alves
next prev parent reply other threads:[~2013-08-27 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 18:12 Pedro Alves
2013-08-23 20:08 ` Joel Brobecker
2013-08-27 11:38 ` Pedro Alves [this message]
2013-08-23 21:37 ` Pierre Muller
2013-08-26 16:52 ` Pedro Alves
2013-08-26 16:54 ` Pedro Alves
2013-08-27 0:50 ` Yao Qi
2013-08-27 11:37 ` 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=521C8FB1.4000601@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).