public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: gcc-4.4 unmasking soon
Date: Thu, 06 Aug 2009 17:57:51 +0300	[thread overview]
Message-ID: <4A7AEF6F.1000507@gentoo.org> (raw)
In-Reply-To: <20090805062118.44cfa677@gentoo.org>

Ryan Hill wrote:
> On Tue, 4 Aug 2009 21:15:57 -0400
> Mark Loeser <halcy0n@gentoo.org> wrote:
> 
>> I'd really like to unmask gcc-4.4.1 soon, as in the next week or so.
>> If you could please install it and test it out, I would appreciate it.
>> Also, if you have any gcc 4.4 porting bugs assigned to a herd that you
>> are a part of, resolving those bugs would help a lot.
>>
>> Thanks to all that have contributed and helped already,
>>
> 
> Also the glibc-2.10 tracker, a lot of which are triggered by the combination
> of it and gcc-4.4.  I admit to massive slacking getting these fixed (mostly
> due to my job sending me to the middle of nowhere for three weeks last month,
> but also Persona 4 (oh that wacky Teddie)).
> 
> https://bugs.gentoo.org/showdependencytree.cgi?id=270353&hide_resolved=1
> 

I'd say what is left unfixed in both trackers gets a CC to treecleaners
in a week or so. Doesn't make sense to keep pkgs that won't build in tree.

-Samuli



  reply	other threads:[~2009-08-06 14:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  1:15 [gentoo-dev] gcc-4.4 unmasking soon Mark Loeser
2009-08-05  4:31 ` Alexey Shvetsov
2009-08-05 12:21 ` [gentoo-dev] " Ryan Hill
2009-08-06 14:57   ` Samuli Suominen [this message]
2009-08-08 15:11 ` Nikos Chantziaras
2009-08-08 17:34   ` Mark Loeser
2009-08-12 21:22   ` James Cloos
2009-08-12 21:39     ` Samuli Suominen
2009-08-12 22:09       ` Nikos Chantziaras
2009-08-13  5:33       ` Ryan Hill
2009-08-13  7:27         ` Samuli Suominen
2009-08-13 23:53           ` 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=4A7AEF6F.1000507@gentoo.org \
    --to=ssuominen@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