From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: hardened glibc and gcc dependencies
Date: Thu, 27 Oct 2011 17:47:07 -0600 [thread overview]
Message-ID: <20111027174707.21c6cdbe@gentoo.org> (raw)
In-Reply-To: CADqQcK4Up37WSOGBgsG-Mn53pLS-RM8jZRA_h9XujQB7YZ6SGw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
On Thu, 27 Oct 2011 23:03:12 +0530
Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
> So, I honestly see no reason why toolchain should not start using EAPI 2.
I await your patch to toolchain.eclass. :P
--
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 --]
next prev parent reply other threads:[~2011-10-27 23:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 9:03 [gentoo-dev] hardened glibc and gcc dependencies "Paweł Hajdan, Jr."
2011-10-27 16:08 ` "Paweł Hajdan, Jr."
2011-10-27 16:49 ` [gentoo-dev] " Duncan
2011-10-27 17:33 ` [gentoo-dev] " Nirbheek Chauhan
2011-10-27 23:47 ` Ryan Hill [this message]
2011-10-27 23:50 ` [gentoo-dev] " Mike Frysinger
2011-10-28 11:36 ` Anthony G. Basile
2011-10-28 17:20 ` Nirbheek Chauhan
2011-10-30 22:24 ` Petteri Räty
2011-10-31 1:04 ` Ryan Hill
2011-10-28 3:03 ` Nirbheek Chauhan
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=20111027174707.21c6cdbe@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