From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Keith Seitz <keiths@redhat.com>,
Doug Evans <dje@google.com>
Subject: Re: 3 weeks to GDB 7.9.1 release?
Date: Fri, 01 May 2015 22:23:00 -0000 [thread overview]
Message-ID: <87mw1oos2o.fsf@redhat.com> (raw)
In-Reply-To: <20150422133231.GB4764@adacore.com> (Joel Brobecker's message of "Wed, 22 Apr 2015 06:32:31 -0700")
On Wednesday, April 22 2015, Joel Brobecker wrote:
> Hello everyone,
>
> Planned date for 7.9.1 re-spin is Wed May, 13th. It appears that
> it's been a fairly smooth sailing for the gdb-7.9-branch since
> GDB 7.9 was released... Our release wiki page
> (https://sourceware.org/gdb/wiki/GDB_7.9_Release) shows that only
> one issue was fixed, and we only have 1 that has been identified
> as blocking:
>
> [Doug?] PR18066 argument "word" seems broken in Command.complete
> (text, word)
This bug has been fixed by:
commit 6d62641c832525382336c1b04731d85cb6c398e7
Author: Sergio Durigan Junior <sergiodj@redhat.com>
Date: Wed Apr 8 18:27:10 2015 -0400
So I closed it and updated the wiki.
On a related note, it doesn't seem to me that this bug should have been
considered as a blocker for this release. It seems to be a small issue
that shouldn't block a GDB release :-). Maybe Doug had other reasons to
consider it a blocker?
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-05-01 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 13:32 Joel Brobecker
2015-04-22 13:59 ` Eli Zaretskii
2015-04-22 14:31 ` Joel Brobecker
2015-04-22 14:38 ` Eli Zaretskii
2015-04-22 15:22 ` Pierre Muller
2015-04-22 17:14 ` Joel Brobecker
2015-05-02 15:33 ` Doug Evans
2015-05-02 22:46 ` Pierre Muller
2015-05-04 12:12 ` Joel Brobecker
2015-05-01 22:23 ` Sergio Durigan Junior [this message]
2015-05-02 15:29 ` Doug Evans
2015-05-06 13:42 ` Joel Brobecker
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=87mw1oos2o.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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).