Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Pedro Alves <palves@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	<gdb-patches@sourceware.org>,	<t@adacore.com>,
	<donb@codesourcery.com>, Yao Qi <yao.qi@arm.com>,
	<antoine.tremblay@ericsson.com>
Subject: Re: GDB 7.12 release - 2016-09-21 update?
Date: Thu, 06 Oct 2016 16:33:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1610061729410.31859@tp.orcam.me.uk> (raw)
In-Reply-To: <8cebd1e3-9131-6467-6145-91ca8051044f@redhat.com>

On Thu, 6 Oct 2016, Pedro Alves wrote:

> >  https://sourceware.org/ml/gdb-patches/2016-10/msg00113.html
> >  https://sourceware.org/ml/gdb-patches/2016-10/msg00114.html
> > 
> > This is the only PR left with target-milestone==7.12.
> 
> ... and ... now closed.
> 
> The buildbots are still catching up on the latest commits, but
> so far so good.  Actually, there's a --disable-build-with-cxx
> build problem on the 7.12 branch right now.  We should fix that
> before we release.

 FYI, I have backported the three changes I made on trunk today, including 
the MIPS FCR fix I mentioned the other day in particular, and also its 
preparatory cosmetic update and an obvious fix for gdb.base/solib-disc.exp 
to work at all.

  Maciej


  reply	other threads:[~2016-10-06 16:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 17:17 Joel Brobecker
2016-09-21 17:52 ` Simon Marchi
2016-10-03 21:10   ` Simon Marchi
2016-09-21 18:30 ` Don Breazeal
2016-09-22 10:40 ` Yao Qi
2016-09-27 18:16 ` Jan Kratochvil
2016-10-06 12:12 ` Pedro Alves
2016-10-06 14:51   ` Pedro Alves
2016-10-06 16:33     ` Maciej W. Rozycki [this message]
2016-10-06 16:41     ` Joel Brobecker
2016-10-07 15:41       ` Pedro Alves
2016-10-07 16:47         ` 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=alpine.DEB.2.00.1610061729410.31859@tp.orcam.me.uk \
    --to=macro@imgtec.com \
    --cc=antoine.tremblay@ericsson.com \
    --cc=brobecker@adacore.com \
    --cc=donb@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=t@adacore.com \
    --cc=yao.qi@arm.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