From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release -- 2019-11-01 Update
Date: Sun, 10 Nov 2019 22:40:00 -0000 [thread overview]
Message-ID: <20191110224010.GI11037@embecosm.com> (raw)
In-Reply-To: <20191104011626.GA24625@adacore.com>
* Joel Brobecker <brobecker@adacore.com> [2019-11-03 17:16:26 -0800]:
> If there are others you think need to be pushed before we branch,
> please let me know. Another way to catch my attention is to use PRs
> with the target milestone being set to "9.1".
I'd was hoping to get these merged into 9.1 as they provide MI access
to some new CLI commands:
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/264
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/265
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/266
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/267
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/268
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/269
Most of these have already had an earlier versions reviewed, so
hopefully there isn't much more that needs doing.
Also this fixes a regressions from earlier versions:
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/511
but this can easily be merged into the release branch later.
thanks,
Andrew
next prev parent reply other threads:[~2019-11-10 22:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 1:16 Joel Brobecker
2019-11-04 21:02 ` Philippe Waroquiers
2019-11-11 17:44 ` Joel Brobecker
2019-11-04 21:26 ` Jonah Graham
2019-11-11 16:05 ` Joel Brobecker
2019-11-05 0:14 ` Christian Biesinger via gdb-patches
2019-11-11 17:48 ` Joel Brobecker
2019-11-15 1:21 ` Christian Biesinger via gdb-patches
2019-11-15 2:17 ` Joel Brobecker
2019-11-19 3:02 ` Christian Biesinger via gdb-patches
2019-11-05 20:54 ` Tom Tromey
2019-11-05 21:33 ` Simon Marchi
2019-11-10 22:40 ` Andrew Burgess [this message]
2019-11-11 17:50 ` 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=20191110224010.GI11037@embecosm.com \
--to=andrew.burgess@embecosm.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