Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] PR remote/17028: GDB+GDBserver hangs on Windows
Date: Wed, 11 Jun 2014 10:17:00 -0000	[thread overview]
Message-ID: <53982CB6.3040704@redhat.com> (raw)
In-Reply-To: <20140611082739.GA4709@adacore.com>

On 06/11/2014 09:27 AM, Joel Brobecker wrote:
>> Here's my current patch to fix PR remote/17028.
>>
>> It fixes the testcase in the PR for me, but I'm not set up
>> for any sort of automated testing on Windows...
> 
> Thanks a lot for the patch. It looks pretty good to me, and it also
> passed testing with our testsuite.

Great!  Looks like target-async still makes it safe and sound to
7.8 then.  Phew!  :-)

I've pushed it in now, with the log issues you pointed out fixed.

>> I'd push this to my github for easier fetching, but github
>> seems to be busted atm...
> 
> I know you were able to push it, but patches sent via git-send-email
> are fine as far as I am concerned. I find it faster to apply via
> git-am, for instance.

It's fine with me too in general.

Though, when calling for testing I like to make it as easy as possible
for someone "driving by" to test (in this case, you, but other people
could want to test as well).  Applying a patch works OK if the touched
code hasn't changed since the patch was generated, otherwise one
either gets to hunt for the base revision or fix conflicts.
A test branch is immune to that.

Since you ran the testing already, and the patch is in
mainline, that's moot now though.  :-)

Thanks,
-- 
Pedro Alves


      reply	other threads:[~2014-06-11 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 18:14 Pedro Alves
2014-06-10 18:18 ` Pedro Alves
2014-06-11  8:27 ` Joel Brobecker
2014-06-11 10:17   ` Pedro Alves [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=53982CB6.3040704@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