From: Simon Marchi <simark@simark.ca>
To: Joel Brobecker <brobecker@adacore.com>, tom@tromey.com
Cc: Jonah Graham <jonah@kichwacoders.com>,
gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
Iain Buclaw <ibuclaw@gdcproject.org>,
Nick Alcock <nick.alcock@oracle.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: Propose we release GDB 9.1 next weekend (Feb 01-02)
Date: Sat, 01 Feb 2020 15:37:00 -0000 [thread overview]
Message-ID: <a4c4c542-1c0b-d875-ca83-7696336ea7f0@simark.ca> (raw)
In-Reply-To: <20200201121720.GA30012@adacore.com>
On 2020-02-01 7:17 a.m., Joel Brobecker wrote:
> For the release, it's indeed a bit on the fence. Given the nature of
> the patch, With a bit of careful review, we should be able to convince
> ourselves that this patch is sufficiently safe, particularly for a .1.
> On the other hand, I think the patch that triggered the regression is
> a fairly minor enhancement (name of the file printed by annotations).
> So perhaps the best way forward is to revert the triggering patch
> from the gdb-9-branch.
Yeah, I think it would be better to revert Tom's patch for the release.
For master, we can take the time to think about what we want long term, and if
a patch like the one I proposed useful.
Simon
prev parent reply other threads:[~2020-02-01 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 15:41 Joel Brobecker
2020-01-26 16:07 ` Eli Zaretskii
2020-01-28 16:43 ` Nick Alcock
2020-01-28 17:06 ` Hannes Domani via gdb-patches
[not found] ` <ee83b6c0-8e18-eb1e-18c8-f9df79b547d7@simark.ca>
2020-01-28 17:37 ` Hannes Domani via gdb-patches
2020-02-01 3:20 ` Jonah Graham
2020-02-01 8:00 ` Simon Marchi
2020-02-01 12:17 ` Joel Brobecker
2020-02-01 12:58 ` Jonah Graham
2020-02-01 13:06 ` Joel Brobecker
2020-02-05 10:08 ` Tom Tromey
2020-02-01 15:45 ` Simon Marchi
2020-02-01 15:37 ` Simon Marchi [this message]
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=a4c4c542-1c0b-d875-ca83-7696336ea7f0@simark.ca \
--to=simark@simark.ca \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.org \
--cc=jonah@kichwacoders.com \
--cc=nick.alcock@oracle.com \
--cc=palves@redhat.com \
--cc=tom@tromey.com \
/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