From: Steve Ellcey <sellcey@imgtec.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: GDB 7.9 branching - 2 weeks to go (Mon, Jan 12th)!
Date: Tue, 06 Jan 2015 16:09:00 -0000 [thread overview]
Message-ID: <1420560568.15691.25.camel@ubuntu-sellcey> (raw)
In-Reply-To: <20141230071500.GF2123@adacore.com>
On Tue, 2014-12-30 at 11:15 +0400, Joel Brobecker wrote:
> Hello,
>
> Just a quick reminder that we're about 2 weeks away from our targeted
> branching date for GDB 7.9. Jan 12th is only a week after what I expect
> to be most people's return to work (Mon Jan 5th), so might be a little
> tight.
>
> But, at the moment, there is no blocking item listed. I will add
> PR gdb/17525 (target-async: breakpoint commands not executed when
> program run from -x script), but only blocking for the release.
> I don't think the problem is severe enough that it warrants blocking
> the branch.
I think PR gdb/17718 should be considered a blocking bug because it
breaks the builds on some systems (depending on what version of GCC is
used to build).
There is some discussion of how it should be fixed in the defect report
and in https://sourceware.org/ml/gdb-patches/2014-12/msg00501.html and
other email threads.
Steve Ellcey
sellcey@imgtec.com
next prev parent reply other threads:[~2015-01-06 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 7:15 Joel Brobecker
2014-12-30 15:42 ` Eli Zaretskii
2014-12-30 15:51 ` Joel Brobecker
2014-12-31 18:11 ` Jan Kratochvil
2015-01-05 4:10 ` Joel Brobecker
2015-01-05 4:13 ` Doug Evans
2015-01-05 4:17 ` Joel Brobecker
2015-01-05 16:07 ` Eli Zaretskii
2015-01-06 16:09 ` Steve Ellcey [this message]
2015-01-06 16:38 ` 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=1420560568.15691.25.camel@ubuntu-sellcey \
--to=sellcey@imgtec.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).