public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: ready GDB 7.9 release?
Date: Tue, 17 Feb 2015 11:15:00 -0000	[thread overview]
Message-ID: <54E322C2.8050503@redhat.com> (raw)
In-Reply-To: <20150217103440.GA10992@adacore.com>

On 02/17/2015 10:34 AM, Joel Brobecker wrote:
> Hello everyone,
> 
> As far as I can tell, we are about ready to make the release.
> There are 2 items on the TODO list for 7.9, but we have the patches
> either approved or already checked in master.
> 
> So I will wait for a couple of days, and if there are no last-minute
> issues, I will check the patches in, and create the 7.9 release.

Would it be OK to merge in the fixes for:

  [Pedro] (Fix racy FAILs of sigall-reverse.exp (and more))

      Now in master, gaining additional exposure. Need to decide whether to push to branch or not based on that.

to the branch?  The series has been on master since 3 Feb, and
I'm not aware of any related regression.  I'll do it today if OK.

(Although exposed by sigall-reverse.exp first, this affects any
"query" done while the target is installed in the event loop.)

Thanks,
Pedro Alves

  reply	other threads:[~2015-02-17 11:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 11:17 GDB 7.9 release update Joel Brobecker
2015-01-28 14:32 ` Doug Evans
2015-01-29  7:19   ` Joel Brobecker
2015-02-03 14:24     ` Pedro Alves
2015-02-03 18:45       ` Eli Zaretskii
2015-02-04  4:11       ` Joel Brobecker
2015-02-04  7:02         ` Phil Muldoon
2015-02-05  5:55           ` Joel Brobecker
2015-02-17 10:34             ` ready GDB 7.9 release? (was: "Re: GDB 7.9 release update") Joel Brobecker
2015-02-17 11:15               ` Pedro Alves [this message]
2015-02-17 11:21                 ` ready GDB 7.9 release? Joel Brobecker
2015-02-17 12:02                   ` Pedro Alves
2015-01-29 16:28 ` GDB 7.9 release update 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=54E322C2.8050503@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).