public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GCC 4.6 unmasking
Date: Sun, 30 Oct 2011 15:22:17 -0600	[thread overview]
Message-ID: <20111030152217.6e8b70aa@gentoo.org> (raw)
In-Reply-To: 20110923203832.5c922e8e@gentoo.org

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

On Fri, 23 Sep 2011 20:38:32 -0600
Ryan Hill <dirtyepic@gentoo.org> wrote:

> Now that I finally have some time for Gentoo.I'd like to get GCC 4.6 unmasked
> sometime in the next month.  Thanks to everyone but me, we only have a few
> bugs remaining on the tracker.  None of them I consider critical except maybe
> mplayer (I'd like someone from media-video to look at applying that patch).
> If you have any bugs open blocking the tracker, please take a look at them
> soon.  If you have a 4.6-related bug that isn't blocking the tracker then
> please add it, even if it's already fixed (the tracker is used to generate a
> fixed-in-version list for the eventual stabilization).
> 
> If you have any issues with 4.6 itself or patches you need applied, now is
> the time to speak up.
> 
> Tracker: https://bugs.gentoo.org/show_bug.cgi?id=gcc-4.6

4.6.2 is now in the tree.  It will be unmasked next weekend.


-- 
fonts, gcc-porting,                  it makes no sense how it makes no sense
toolchain, wxwidgets                           but i'll take it free anytime
@ gentoo.org                EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

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

  parent reply	other threads:[~2011-10-30 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-24  2:38 [gentoo-dev] GCC 4.6 unmasking Ryan Hill
2011-09-25 13:10 ` [gentoo-dev] " Diego Elio Pettenò
2011-09-26  2:18   ` Ryan Hill
2011-10-30 21:22 ` Ryan Hill [this message]
2011-11-12  2:50   ` Ryan Hill

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=20111030152217.6e8b70aa@gentoo.org \
    --to=dirtyepic@gentoo.org \
    --cc=gentoo-dev@lists.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