From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: 3 weeks to GDB 7.9.1 release?
Date: Wed, 22 Apr 2015 13:32:00 -0000 [thread overview]
Message-ID: <20150422133231.GB4764@adacore.com> (raw)
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)
Anything else that should be seen as blocking for 7.9.1?
This is a good opportunity to remind everyone that patches to
release branches, once the first official release has been made,
must be documented on that page. Otherwise, I will not be able
to provide the full list of improvements that this release brings.
I reviewed the commits on that branch, and identified 2 patches that
have been pushed without following the full procedure, and I will be
emailing those authors privately. But the branch is polluted by
a number of date-update commits, so if you know you've made a change
and forgot to follow the procedure, it's not too late: You need a PR,
which you can create if you don't have one already, and then just add
a one-line description to the wiki page shown above (that description
can simply be the subject line of the PR).
Thank you,
--
Joel
next reply other threads:[~2015-04-22 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 13:32 Joel Brobecker [this message]
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
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=20150422133231.GB4764@adacore.com \
--to=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