From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 8.3 release update (2019-03-25)
Date: Tue, 26 Mar 2019 20:46:00 -0000 [thread overview]
Message-ID: <83k1gll5x8.fsf@gnu.org> (raw)
In-Reply-To: <20190326204042.GA6837@adacore.com> (message from Joel Brobecker on Tue, 26 Mar 2019 13:40:42 -0700)
> Date: Tue, 26 Mar 2019 13:40:42 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > All the problems I knew about are fixed, but I wonder whether we need
> > another pretest, since so many non-trivial changes went in.
>
> Yeah, I saw those, and unfortunately saw them too late to raise
> a flag. Since they are in, now, might as well keep them.
I didn't mean to say that those changes shouldn't have been admitted.
They all fixed bugs caused by new features in this release. I just
meant to say that the changes were not trivial, so maybe we have
caused regressions with them.
> I can create another pre-release -- but I'll wait for the various
> issues identified before doing so. Might as well include those in
> the next pre-release.
Right. Thanks.
next prev parent reply other threads:[~2019-03-26 20:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 20:43 Joel Brobecker
2019-03-25 20:51 ` Eli Zaretskii
2019-03-26 20:40 ` Joel Brobecker
2019-03-26 20:46 ` Eli Zaretskii [this message]
2019-03-25 22:26 ` Sergio Durigan Junior
2019-03-26 20:48 ` Joel Brobecker
2019-03-26 21:31 ` Sergio Durigan Junior
2019-03-26 22:46 ` Joel Brobecker
2019-03-25 22:29 ` Simon Marchi
2019-03-26 21:15 ` Pedro Franco de Carvalho
2019-03-26 22:21 ` Joel Brobecker
2019-03-27 13:30 ` Tom Tromey
2019-03-27 19:47 ` Pedro Franco de Carvalho
2019-03-27 19:51 ` Pedro Alves
2019-03-28 17:36 ` 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=83k1gll5x8.fsf@gnu.org \
--to=eliz@gnu.org \
--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