From: Ryan Hill <dirtyepic.sk@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GCC 4.1.1 testing/stablization and glibc 2.4
Date: Sun, 16 Jul 2006 16:06:20 -0600 [thread overview]
Message-ID: <e9ed9b$umu$1@sea.gmane.org> (raw)
In-Reply-To: <e9c51q$mfo$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
Ryan Hill wrote:
> Just an update - I've finished most major desktop stuff for x86 without any
> problems. I'm moving onto stuff that's already on the tracker and is fixed in
> testing but not stable. Rather than open and track a ton of new bugs, I'd like
> to reopen the original ~arch bugs and request a backport or stabilization at the
> maintainer's discretion.
I changed my mind. Reopening these just creates too much random bugspam.
--de.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-16 22:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 21:56 [gentoo-dev] GCC 4.1.1 testing/stablization and glibc 2.4 Chris Gianelloni
2006-06-27 22:32 ` Donnie Berkholz
2006-06-28 0:20 ` Mike Frysinger
2006-06-27 22:33 ` Dan Meltzer
2006-07-01 18:18 ` [gentoo-dev] " Ryan Hill
2006-07-02 14:13 ` Chris Gianelloni
2006-07-16 1:33 ` Ryan Hill
2006-07-16 22:06 ` Ryan Hill [this message]
2006-07-16 6:06 ` R 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='e9ed9b$umu$1@sea.gmane.org' \
--to=dirtyepic.sk@gmail.com \
--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