Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Andrew Burgess" <aburgess@broadcom.com>
To: gdb-patches@sourceware.org
Subject: PING: [PATCH] Remove deprecated_command_loop_hook
Date: Thu, 29 Aug 2013 10:48:00 -0000	[thread overview]
Message-ID: <521F26CB.3070209@broadcom.com> (raw)
In-Reply-To: <521558B5.6070909@broadcom.com>

Ping!

I know the gdbtk patch has not yet been merged, but the patch I posted
for them is not huge, nor should it prove controversial, it's in the
same style as this patch for core gdb.

Thanks,
Andrew

On 22/08/2013 1:17 AM, Andrew Burgess wrote:
> On 21/08/2013 7:56 PM, Stan Shebs wrote:
>> On 8/21/13 11:09 AM, Andrew Burgess wrote:
>>> Small patch to remove deprecated_command_loop_hook.
>>>
>>> OK to apply?
>>
>> FYI, this hook is essential to gdbtk, which uses it to connect into its
>> main command loop.  It's not obvious to me whether it would be easy or
>> hard to rewrite gdbtk to not need it.
> 
> It looks like deprecated_command_loop_hook is used in gdbtk just like
> it's used in the MI code.  I've submitted a patch to gdbtk that removes
> the use:
>   http://sourceware.org/ml/insight/2013-q3/msg00029.html
> 
> Thanks,
> Andrew
> 
> 
> 
> 



  reply	other threads:[~2013-08-29 10:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 18:09 Andrew Burgess
2013-08-21 18:56 ` Stan Shebs
2013-08-22  0:18   ` Andrew Burgess
2013-08-29 10:48     ` Andrew Burgess [this message]
2013-08-29 14:34       ` PING: " Pedro Alves
2013-08-29 16:27         ` Andrew Burgess
2013-08-29 16:42           ` remove the use of deprecated_command_loop_hook from the MI code. (was: Re: Remove deprecated_command_loop_hook) Pedro Alves
2013-08-29 17:17             ` remove the use of deprecated_command_loop_hook from the MI code Andrew Burgess

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=521F26CB.3070209@broadcom.com \
    --to=aburgess@broadcom.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