From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: 3 weeks to GDB 7.9.1 release?
Date: Wed, 22 Apr 2015 13:59:00 -0000 [thread overview]
Message-ID: <83y4lk2ria.fsf@gnu.org> (raw)
In-Reply-To: <20150422133231.GB4764@adacore.com>
> Date: Wed, 22 Apr 2015 06:32:31 -0700
> From: Joel Brobecker <brobecker@adacore.com>
>
> 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)
>
> Anything else that should be seen as blocking for 7.9.1?
Not really blocking, but would someone please help me get these
annoyances fixed upstream, so that I don't need to continue fixing
them in every GDB release?
http://lists.gnu.org/archive/html/bug-binutils/2015-03/msg00115.html
TIA
next prev parent reply other threads:[~2015-04-22 13:59 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 [this message]
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
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=83y4lk2ria.fsf@gnu.org \
--to=eliz@gnu.org \
--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).