From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release -- 2019-11-01 Update
Date: Tue, 05 Nov 2019 20:54:00 -0000 [thread overview]
Message-ID: <87h83irqm5.fsf@tromey.com> (raw)
In-Reply-To: <20191104011626.GA24625@adacore.com> (Joel Brobecker's message of "Sun, 3 Nov 2019 17:16:26 -0800")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> Objective #1 is to branch. Before we do so, we need to identify
Joel> the list of changes that are large and/or tricky enough that we'd
Joel> want those change to be done in master, prior to branching.
Joel> Below is the list of patches that I know about. If your name is
Joel> next to it, it means you're the patch's champion ;-).
I have a lot of patches pending in gerrit. Most of them aren't really
important for any particular release, though this one is regression fix:
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/371
Whether it goes in before or after the branch is made isn't too
important to me.
Plus, there's the series to fix the windows-nat crash.
Tom
next prev parent reply other threads:[~2019-11-05 20:54 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 [this message]
2019-11-05 21:33 ` Simon Marchi
2019-11-10 22:40 ` Andrew Burgess
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=87h83irqm5.fsf@tromey.com \
--to=tom@tromey.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