Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Pedro Alves <palves@redhat.com>,
	Andrew Burgess	<andrew.burgess@embecosm.com>,
	"gdb-patches@sourceware.org"	<gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [8.3 backport] Supress SIGTTOU when handling errors
Date: Mon, 05 Aug 2019 10:59:00 -0000	[thread overview]
Message-ID: <64430CB3-E213-4EA4-8A73-B67D41DC6692@arm.com> (raw)
In-Reply-To: <507d074a-75ef-b3b1-f5f5-7230ded52685@suse.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1023 bytes --]



> On 2 Aug 2019, at 17:05, Tom de Vries <tdevries@suse.de> wrote:
> 
> On 28-05-19 11:39, Alan Hayward wrote:
>> 
>> 
>>> On 27 May 2019, at 19:03, Pedro Alves <palves@redhat.com> wrote:
>>> 
>>> On 5/26/19 11:42 PM, Andrew Burgess wrote:
>>>> * Alan Hayward <Alan.Hayward@arm.com> [2019-05-24 12:36:43 +0000]:
>>>> 
>>> 
>>>>> Ok, agreed.
>>>>> 
>>>>> Any objections to me pushing the original patch then?
>>>> 
>>>> Not from me.
>>>> 
>>>> Sorry for any delay I caused in getting the patch merged.
>>> 
>>> Not at all.  It was an interesting discussion and revealed that we
>>> need to clean up and clarify some comments at least.
>>> 
>>> Thanks,
>>> Pedro Alves
>> 
>> Ditto with what Pedro said, and pushed.
>> 
> 
> Hi,
> 
> OK to backport to 8.3?
> 
> The patch applies cleanly, and causes no regressions on x86_64-linux.
> 

I’ve got no issues with this one either, but don’t have the powers to approve.


> Thanks,
> - Tom
> 
> 

\x16º&Öéj×!zÊÞ¶êçמýëÙb²Ö«r\x18\x1dn–­r\x17¬

  reply	other threads:[~2019-08-05 10:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 15:51 [PATCH] " Alan Hayward
2019-05-16 18:06 ` Andrew Burgess
2019-05-16 18:30   ` Andrew Burgess
2019-05-23 20:33     ` Pedro Alves
2019-05-17 12:47   ` Alan Hayward
2019-05-18  9:10     ` Andrew Burgess
2019-05-23 20:32   ` Pedro Alves
2019-05-24  8:54     ` Alan Hayward
     [not found]       ` <7483f478-44d2-b2ce-b0cb-3e984054305a@redhat.com>
2019-05-24 12:36         ` Alan Hayward
2019-05-24 13:15           ` Pedro Alves
2019-05-26 22:43           ` Andrew Burgess
2019-05-27 18:03             ` Pedro Alves
2019-05-28  9:39               ` Alan Hayward
2019-08-02 16:05                 ` [8.3 backport] " Tom de Vries
2019-08-05 10:59                   ` Alan Hayward [this message]
2019-08-05 17:33                   ` Tom Tromey
2019-05-18 13:42 ` [PATCH] " Andreas Schwab
2019-05-19 22:06   ` Andrew Burgess
2019-05-20  8:44     ` Alan Hayward
     [not found]       ` <20190520091157.GC2568@embecosm.com>
2019-05-20  9:49         ` Pedro Alves
2019-05-23 20:35         ` 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=64430CB3-E213-4EA4-8A73-B67D41DC6692@arm.com \
    --to=alan.hayward@arm.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=palves@redhat.com \
    --cc=tdevries@suse.de \
    /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