public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@gentoo.org, gentoo-dev-announce@gentoo.org
Subject: [gentoo-dev-announce] GCC 4.7 unmasking
Date: Sat, 29 Sep 2012 22:07:45 -0600	[thread overview]
Message-ID: <20120929220745.4a4b1490.dirtyepic@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

I just added gcc-4.7.2 to the tree, and I'd like to unmask it in a couple
weeks.  I don't see anything I'd consider a blocker on the tracker*, but
95 open bugs is still a lot.  If you have a bug blocking the tracker please
take a look at it soon.  Many of these are trivial and could make good
bugsday projects (if we even do bugsdays anymore).

* https://bugs.gentoo.org/390247


PS. still looking for a gcc maintainer who isn't me.

-- 
gcc-porting
toolchain, wxwidgets          we were never more here, expanse getting broader
@ gentoo.org                          but bigger boats been done by less water

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2012-09-30  6:03 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=20120929220745.4a4b1490.dirtyepic@gentoo.org \
    --to=dirtyepic@gentoo.org \
    --cc=gentoo-dev-announce@gentoo.org \
    --cc=gentoo-dev@gentoo.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