From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release: Start of stabilization period ?
Date: Mon, 14 Oct 2019 17:44:00 -0000 [thread overview]
Message-ID: <87k197te6i.fsf@tromey.com> (raw)
In-Reply-To: <20191012191938.GA2675@adacore.com> (Joel Brobecker's message of "Sat, 12 Oct 2019 15:19:38 -0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> Are there any issues that people would like to be fixed, before
Joel> we release GDB 9.1?
Based on the other follow-ups, I think it would be good if we could
review any pending patches before the release. We could pick some
cutoff date and say that any patch before that date is eligible for
holding up the release, provided it is pinged in a timely way.
Another question I have is whether we want to try to finish the "move
gdbserver" project. The first step (moving gnulib) is in, but recall
that this broke in-tree builds -- which would be the major reason to
wait for this. A couple subsequent steps (moving readline and moving
gdbsupport) have been submitted, but the final step has not.
Tom
next prev parent reply other threads:[~2019-10-14 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 19:19 Joel Brobecker
2019-10-13 1:19 ` Christian Biesinger via gdb-patches
2019-10-13 13:58 ` Tom de Vries
2019-10-15 15:20 ` Joel Brobecker
2019-10-15 15:23 ` Tom de Vries
2019-10-15 15:37 ` Joel Brobecker
2019-10-15 15:16 ` Joel Brobecker
2019-10-13 14:35 ` Philippe Waroquiers
2019-10-15 15:37 ` Joel Brobecker
2019-10-14 17:44 ` Tom Tromey [this message]
2019-10-15 15:53 ` 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=87k197te6i.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