From: Jakub Jelinek <jakub@redhat.com>
To: gcc@gcc.gnu.org
Subject: GCC 4.6.1 Status Report (2011-03-26)
Date: Sat, 26 Mar 2011 09:50:00 -0000 [thread overview]
Message-ID: <20110326064349.GE11563@sunsite.ms.mff.cuni.cz> (raw)
Status
======
GCC 4.6.0 release tarballs have been uploaded to gcc.gnu.org
and ftp.gnu.org, the 4.6 branch is open again for commits under
the usual release branch rules.
I'll announce the release once mirrors had some time to download it.
GCC 4.6.1 is planned for roughly late May, unless some unexpected
severe bug forces us to release it earlier.
Quality Data
============
Priority # Change from Last Report
-------- --- -----------------------
P1 0 0
P2 85 + 4
P3 20 + 17
-------- --- -----------------------
Total 105 + 21
Previous Report
===============
http://gcc.gnu.org/ml/gcc/2011-03/msg00176.html
The next report will be sent by Joseph.
reply other threads:[~2011-03-26 6:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110326064349.GE11563@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.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).