From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: hardened glibc and gcc dependencies
Date: Fri, 28 Oct 2011 01:50:46 +0200 [thread overview]
Message-ID: <CAJaTeToh=qQ4ZKbSbnmSeKsfOboqFg5_dRVY1WTrTDu0b3cvyA@mail.gmail.com> (raw)
In-Reply-To: <20111027174707.21c6cdbe@gentoo.org>
On Fri, Oct 28, 2011 at 01:47, Ryan Hill wrote:
> On Thu, 27 Oct 2011 23:03:12 +0530 Nirbheek Chauhan wrote:
>> So, I honestly see no reason why toolchain should not start using EAPI 2.
>
> I await your patch to toolchain.eclass. :P
i wouldn't bother as it's most likely not going to be accepted at this time
(i haven't kept up-to-date with the hardened threads as i'm traveling atm)
-mike
next prev parent reply other threads:[~2011-10-27 23:51 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 ` [gentoo-dev] " Ryan Hill
2011-10-27 23:50 ` Mike Frysinger [this message]
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='CAJaTeToh=qQ4ZKbSbnmSeKsfOboqFg5_dRVY1WTrTDu0b3cvyA@mail.gmail.com' \
--to=vapier@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