From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb-7.11.1 re-spin update
Date: Wed, 27 Apr 2016 19:36:00 -0000 [thread overview]
Message-ID: <20160427193624.GA25868@host1.jankratochvil.net> (raw)
In-Reply-To: <20160425214951.GA4079@adacore.com>
On Mon, 25 Apr 2016 23:49:51 +0200, Joel Brobecker wrote:
> Looking at the wiki page for that release branch
> (https://sourceware.org/gdb/wiki/GDB_7.11_Release), I see
> there are currently 2 items marked critical before 7.11.1
> can be released:
[...]
> PR remote/19863
> (7.10 regression: gdb remote.c due to "setfs" with gdbserver <=7.9)
I have checked in master + 7.11 branch and closed this PR now.
Jan
next prev parent reply other threads:[~2016-04-27 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 21:50 Joel Brobecker
2016-04-26 12:16 ` Pedro Alves
2016-05-02 15:46 ` Joel Brobecker
2016-05-02 17:23 ` Pedro Alves
2016-05-02 19:38 ` Joel Brobecker
2016-05-02 19:41 ` Pedro Alves
2016-05-02 21:16 ` Joel Brobecker
2016-05-02 21:30 ` Pedro Alves
2016-05-05 13:49 ` Joel Brobecker
2016-04-27 19:36 ` Jan Kratochvil [this message]
2016-05-03 14:19 ` Simon Marchi
2016-05-03 14:31 ` Joseph Myers
2016-05-03 15:01 ` Simon Marchi
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=20160427193624.GA25868@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--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