Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Andrew Burgess" <aburgess@broadcom.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] Remove remaining uses of deprecated_throw_reason.
Date: Wed, 31 Jul 2013 12:45:00 -0000	[thread overview]
Message-ID: <51F906EB.8080205@broadcom.com> (raw)
In-Reply-To: <51F81221.7000907@redhat.com>

On 30/07/2013 8:21 PM, Pedro Alves wrote:
> On 07/30/2013 05:12 PM, Andrew Burgess wrote:
>> This removes the final uses of deprecated_throw_reason.  In each case I've
>> replaced the use of deprecated_throw_reason with a call to quit.  The only
>> change this will have is that the user will now see a "Quit" message,
>> however this seems pretty appropriate to me, what do you think?
>>
>> OK to apply?
> 
> OK.

Committed ahead of patch 2/4 as they are independent.

Thanks,
Andrew



  reply	other threads:[~2013-07-31 12:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 16:09 [PATCH 0/4] Remove deprecated_throw_reason Andrew Burgess
2013-07-30 16:10 ` [PATCH 1/4] Remove deprecated_throw_reason from internal_verror Andrew Burgess
2013-07-30 19:08   ` Pedro Alves
2013-07-31 10:52     ` Andrew Burgess
2013-07-30 16:11 ` [PATCH 2/4] Remove deprecated_throw_reason from mips_error Andrew Burgess
2013-07-30 19:14   ` Pedro Alves
2013-07-31 12:37     ` Andrew Burgess
2013-07-31 14:44       ` Pedro Alves
2013-07-31 15:37         ` Andrew Burgess
2013-07-30 16:12 ` [PATCH 3/4] Remove remaining uses of deprecated_throw_reason Andrew Burgess
2013-07-30 19:21   ` Pedro Alves
2013-07-31 12:45     ` Andrew Burgess [this message]
2013-07-30 16:13 ` [PATCH 4/4] Remove deprecated_throw_reason Andrew Burgess
2013-07-30 19:22   ` Pedro Alves
2013-07-31 15:45     ` 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=51F906EB.8080205@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