From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] remote.c, clean-up mix-up
Date: Thu, 06 May 2010 00:28:00 -0000 [thread overview]
Message-ID: <4BE20D1F.4040604@vmware.com> (raw)
In-Reply-To: <201005060118.26368.pedro@codesourcery.com>
Pedro Alves wrote:
> On Thursday 06 May 2010 00:44:35, Pedro Alves wrote:
>> Here's what I'm testing.
>
> No regressions against x86_64-linux gdbserver.
>
>> 2010-05-05 Pedro Alves <pedro@codesourcery.com>
>>
>> * remote.c (clear_threads_parsing_context): New.
>> (remote_threads_info): Delele unused null_cleanup. Install a
>> cleanup to clear the threads_parsing_context in case parsing
>> throws.
>
> Applied as below with a little comment added and typo in
> changelog fixed.
>
Thanks a lot for following through!
Michael
prev parent reply other threads:[~2010-05-06 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 22:37 Michael Snyder
2010-05-05 23:08 ` Pedro Alves
2010-05-05 23:44 ` Pedro Alves
2010-05-06 0:18 ` Pedro Alves
2010-05-06 0:28 ` Michael Snyder [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=4BE20D1F.4040604@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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