From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PING] [PATCH 0/3] Fix for PR 17808 and some related changes
Date: Wed, 04 Feb 2015 18:13:00 -0000 [thread overview]
Message-ID: <87iofhwnns.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <20150204035942.GM4525@adacore.com> (Joel Brobecker's message of "Wed, 4 Feb 2015 07:59:42 +0400")
On Wed, Feb 04 2015, Joel Brobecker wrote:
>> Sounds good to me, but I have a counter proposal.
>>
>> How about we push it all to master now? That'd give it exposure on
>> both auto testers and on others' machines immediately. We can always
>> address any additional comments as follow ups, of course. The main
>> difference is that the series would be exposed to testing one
>> extra week. Then if we see no fall out, we'd have a little more
>> confidence pushing to 7.9.
>
> Sounds even better to me.
>
> Andreas, please push your changes now.
Done. Thanks for your support!
BTW, do we also want to get the test case upstream that triggered this
PR? Jan posted it here:
https://sourceware.org/ml/gdb-patches/2015-01/msg00199.html
next prev parent reply other threads:[~2015-02-04 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 16:28 Andreas Arnez
2015-02-02 3:50 ` Joel Brobecker
2015-02-03 14:19 ` Pedro Alves
2015-02-04 3:59 ` Joel Brobecker
2015-02-04 18:13 ` Andreas Arnez [this message]
2015-02-20 3:09 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2015-01-15 15:22 Andreas Arnez
2015-01-22 11:38 ` [PING] " Andreas Arnez
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=87iofhwnns.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).