From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org,
Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: FYI: GDB 7.10.1 release still planned end of Nov
Date: Wed, 28 Oct 2015 19:46:00 -0000 [thread overview]
Message-ID: <5631005E.9070208@redhat.com> (raw)
In-Reply-To: <20151028164757.GC4009@adacore.com>
On 10/28/2015 04:47 PM, Joel Brobecker wrote:
> Hello everyone,
>
> Just a quick message to say that we're still planning a 7.10.1
> release by end of next month. For now, there have been only
> 2 fixes pushed to the branch:
>
> * PR remote/18965
> (new vforkdone stop reply should indicate parent process ID)
> * PR gdb/18957
> (build failure in linux-namespaces.c due to setns static declaration)
>
> If there are other fixes you'd like to be made on the branch for that
> release, it's time to let us know by updating the wiki page used to
> track the releases off that branch:
>
> https://sourceware.org/gdb/wiki/GDB_7.10_Release
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?
Thanks,
Pedro Alves
>
> Please remember that *all* fixes pushed to the gdb-7.10-branch
> require a corresponding bugzilla PR where we fill information on
> the fix being made, and the wiki page above also needs to be updated
> to reference that PR. This helps me quite a bit when I compose
> the release announcement (thank you!).
>
> Next reminder will be a couple of weeks ahead of the planned release.
>
> Cheers :)
>
next prev parent reply other threads:[~2015-10-28 17:05 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 [this message]
2015-11-12 18:44 ` Joel Brobecker
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=5631005E.9070208@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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