public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: tromey@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 9.1 Release: Creating the branch on *WED* Dec 11th!
Date: Fri, 13 Dec 2019 07:51:00 -0000	[thread overview]
Message-ID: <83immk8xyl.fsf@gnu.org> (raw)
In-Reply-To: <20191212223601.GA13716@adacore.com> (message from Joel Brobecker	on Thu, 12 Dec 2019 23:36:01 +0100)

> Date: Thu, 12 Dec 2019 23:36:01 +0100
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > I think these should be dropped from the release.  They've required
> > fairly extensive rewriting.  Also, I haven't completed the rewrites from
> > the last round of reviews, and due to work stuff I'm not likely to in
> > the next couple of weeks.
> 
> Thanks for the update on those. It seems wise to drop them indeed.

Does this mean the pretest published yesterday doesn't represent the
upcoming release well enough, as these changesets are still part of
it?  If so, can we please have a better pretest soon?  I planned on
building the pretest on MinGW soon, as I've seen many changes that
might "need work" in the MinGW port.

TIA

  reply	other threads:[~2019-12-13  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-08  1:05 Joel Brobecker
2019-12-08 12:38 ` Philippe Waroquiers
2019-12-10 14:49 ` Tom Tromey
2019-12-12 22:36   ` Joel Brobecker
2019-12-13  7:51     ` Eli Zaretskii [this message]
2019-12-13 23:47       ` Joel Brobecker
2019-12-14  7:48         ` Eli Zaretskii
2019-12-14 15:26           ` 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=83immk8xyl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).