From: Jeff Law <jeffreyalaw@gmail.com>
To: waffl3x <waffl3x@protonmail.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Stage 4 date
Date: Sun, 7 Jan 2024 15:12:32 -0700 [thread overview]
Message-ID: <56f14678-20d5-4cff-85b5-7a12c13ef22f@gmail.com> (raw)
In-Reply-To: <RSY0mUqRnoVY60uIU-QLPotA6xJVGQe3j30ESNiYrTVesMh193V4QT-R-sRcwZnWN0CIWraRdQ8TW6meyZt3rvAnTFbsvz5tSRDZ3gg25Sk=@protonmail.com>
On 1/7/24 08:48, waffl3x via Gcc wrote:
> https://gcc.gnu.org/develop.html#timeline
> The date for stage 4 is listed as the 8th on here, is that date final?
> There is at least 1 patch pending (mine) that is complete but Jason
> Merril hasn't been active for a few days. He had expressed to me that
> he expected the date to be next week on the 14th. Is it possible to
> push back the date for stage 4 a little bit? I've been working hard on
> my patch and would be very disappointed if it did not make it in for
> GCC14.
Note there is generally allowances made for patches that were posted
before the deadline, but are still going through the review/iterate process.
Jeff
next prev parent reply other threads:[~2024-01-07 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 15:48 waffl3x
2024-01-07 22:12 ` Jeff Law [this message]
2024-01-07 22:22 ` Jakub Jelinek
2024-01-07 23:39 ` waffl3x
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=56f14678-20d5-4cff-85b5-7a12c13ef22f@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=waffl3x@protonmail.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).