From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: FYI: GDB 7.10.1 release still planned end of Nov
Date: Thu, 12 Nov 2015 18:44:00 -0000 [thread overview]
Message-ID: <20151112184430.GA4646@adacore.com> (raw)
In-Reply-To: <5631005E.9070208@redhat.com>
Hello,
Just a quick reminder - we are now 2 weeks away from our planned
date for 7.10.1.
> I think we should have this one in too:
>
> [patch] fix misparsing in remote_parse_stop_reply
> https://sourceware.org/ml/gdb-patches/2015-08/msg00413.html
>
> Sandra, could you handle that one?
No answer from Sandra, but I've added it to the the Wiki.
Sandra - if you want to push it to the branch, remember that
we need to recreate a PR for it. For now, I've replaced the PR
numbers by ??? in the GDB 7.10 release wiki page...
Thank you!
--
Joel
next prev parent reply other threads:[~2015-11-12 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 19:36 Joel Brobecker
2015-10-28 19:46 ` Pedro Alves
2015-11-12 18:44 ` Joel Brobecker [this message]
2015-11-12 18:55 ` Sandra Loosemore
2015-11-12 19:38 ` Joel Brobecker
2015-11-14 0:23 ` Sandra Loosemore
2015-11-14 8:58 ` Andreas Schwab
2015-11-15 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=20151112184430.GA4646@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sandra@codesourcery.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