Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org, DJ Delorie <dj@redhat.com>
Subject: Re: GDB 8.0 release update (2017-05-19)
Date: Tue, 30 May 2017 08:44:00 -0000	[thread overview]
Message-ID: <83inkient7.fsf@gnu.org> (raw)
In-Reply-To: <83a862m8o5.fsf@gnu.org> (message from Eli Zaretskii on Wed, 24	May 2017 21:06:18 +0300)

> Date: Wed, 24 May 2017 21:06:18 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> CC: gdb-patches@sourceware.org
> 
> > Date: Wed, 24 May 2017 08:49:39 -0700
> > From: Joel Brobecker <brobecker@adacore.com>
> > Cc: gdb-patches@sourceware.org
> > 
> > > They are in the works, but not there yet.  I hope they will be ready
> > > by the date you want to make the release, but I cannot be sure.
> > 
> > As far as I can tell, at least 1 patch is still being discussed,
> > and the others should be in; is that correct?
> 
> I think there are two not yet committed into libiberty.  There's also
> one for GDB.
> 
> > Would you mind dropping me a note when we're good to go for the
> > release?
> 
> Will do.

We are not yet there, but here's an update: 2 out of 3 libiberty
changes are committed to the GCC tree, the 3rd should be there soon, I
hope.

Once that happens, I guess I should push them all to the GDB master,
and then cherry-pick to the 8.0 branch, is that right?


  reply	other threads:[~2017-05-30  8:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 18:30 Joel Brobecker
2017-05-19 20:57 ` Eli Zaretskii
2017-05-24 15:49   ` Joel Brobecker
2017-05-24 18:06     ` Eli Zaretskii
2017-05-30  8:44       ` Eli Zaretskii [this message]
2017-05-30 12:45         ` Joel Brobecker
2017-05-31  6:50           ` Eli Zaretskii
2017-06-04 17:14             ` 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=83inkient7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=dj@redhat.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