public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: Jan Hubicka <hubicka@ucw.cz>
Subject: Re: GCC 4.9.3 Status Report (2015-06-17) - branch frozen for release
Date: Wed, 17 Jun 2015 09:59:00 -0000	[thread overview]
Message-ID: <5581409B.9050902@suse.cz> (raw)
In-Reply-To: <20150617084442.GK10247@tucnak.redhat.com>

On 06/17/2015 10:44 AM, Jakub Jelinek wrote:
> The GCC 4.9 branch is now frozen for preparing of a release candidate for
> GCC 4.9.3.  All changes to the branch require release manager approval
> from now on until 4.9.3 is released.
> 
> I'll announce the GCC 4.9.3 release candidate once it is ready.
> 

Hello.

I've been waiting for any comment related to PR66394, which is also affected in 4.9 branch.
Link: https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00739.html

Would you be interested in the fix, or would it be better to postpone it for the next release?

Thanks,
Martin

      reply	other threads:[~2015-06-17  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  8:57 Jakub Jelinek
2015-06-17  9:59 ` Martin Liška [this message]

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=5581409B.9050902@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    /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).