From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>, Martin Sebor <msebor@gmail.com>
Cc: Jason Merrill <jason@redhat.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] have chkp skip flexible member arrays (PR #79986)
Date: Tue, 21 Mar 2017 15:17:00 -0000 [thread overview]
Message-ID: <fdcecbd0-960c-2c4d-ec46-976772fcdfc5@redhat.com> (raw)
In-Reply-To: <20170321151549.GX11094@tucnak>
On 03/21/2017 09:15 AM, Jakub Jelinek wrote:
> On Tue, Mar 21, 2017 at 09:08:49AM -0600, Martin Sebor wrote:
>> As I understand the schedule, the release is expected sometime
>> in early April. I leave on April 2 for a week, so I have only
>> until then. I don't think that leaves enough time. I'd be
>> uncomfortable taking on a project this late in the cycle that
>> could put the release in jeopardy, or that I might have to
>> rely on others to finish up.
>
> The release is expected when it is ready. We still have 8 P1s,
> so we don't meet the release criteria, and have way too many P2-P3s,
> early April is very unlikely, late April is much more likely than that.
Late April is consistent with my estimate of when the release will be
ready as well.
jeff
next prev parent reply other threads:[~2017-03-21 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 23:04 Martin Sebor
2017-03-20 23:51 ` Jason Merrill
2017-03-20 23:58 ` Martin Sebor
2017-03-21 4:27 ` Jason Merrill
2017-03-21 15:08 ` Martin Sebor
2017-03-21 15:15 ` Jakub Jelinek
2017-03-21 15:17 ` Jeff Law [this message]
2017-03-21 15:46 ` Marek Polacek
2017-03-21 23:56 ` Martin Sebor
2017-03-21 19:33 ` Jason Merrill
2017-03-29 23:29 ` Martin Sebor
2017-04-07 16:50 ` Jason Merrill
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=fdcecbd0-960c-2c4d-ec46-976772fcdfc5@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=msebor@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).