From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] My wishlist for EAPI 5
Date: Sat, 23 Jun 2012 12:37:59 +0100 [thread overview]
Message-ID: <20120623123759.03d19277@googlemail.com> (raw)
In-Reply-To: <20120623113809.1641.qmail@stuge.se>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
On Sat, 23 Jun 2012 13:38:09 +0200
Peter Stuge <peter@stuge.se> wrote:
> If you don't understand something of what thus far has been written,
> then why not ask specific questions to fill those gaps, and move on?
The multilib material isn't at the point where specific questions can be
asked. Brian's description of it as an "opaque list of things" is
pretty much spot on. That's why we want a GLEP and a PMS diff -- an
attempt at those might bring this to the point where we can say
something other than "huh?".
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-06-23 11:43 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 20:25 [gentoo-dev] My wishlist for EAPI 5 Richard Yao
2012-06-20 20:35 ` Ciaran McCreesh
2012-06-20 20:50 ` Richard Yao
2012-06-20 20:54 ` Ciaran McCreesh
2012-06-20 21:02 ` Richard Yao
2012-06-20 21:10 ` Ciaran McCreesh
2012-06-20 21:05 ` Richard Yao
2012-06-20 21:12 ` Ciaran McCreesh
2012-06-20 21:34 ` Richard Yao
2012-06-21 8:29 ` [gentoo-dev] " Duncan
2012-06-21 9:23 ` Richard Yao
2012-06-22 0:38 ` Richard Yao
2012-06-22 5:30 ` Duncan
2012-06-22 5:55 ` Michał Górny
2012-06-22 6:20 ` Ben de Groot
2012-06-20 21:43 ` [gentoo-dev] " Justin
2012-06-21 6:08 ` Pacho Ramos
2012-06-21 7:00 ` Ciaran McCreesh
2012-06-21 7:25 ` Pacho Ramos
2012-06-21 7:39 ` Ciaran McCreesh
2012-06-23 7:53 ` Pacho Ramos
2012-06-23 9:38 ` Ciaran McCreesh
2012-06-23 9:53 ` Peter Stuge
2012-06-23 10:24 ` Pacho Ramos
2012-06-23 10:30 ` Pacho Ramos
2012-06-23 10:31 ` Ciaran McCreesh
2012-06-23 11:05 ` Pacho Ramos
2012-06-23 11:14 ` Ciaran McCreesh
2012-06-23 11:38 ` Peter Stuge
2012-06-23 11:37 ` Ciaran McCreesh [this message]
2012-06-23 11:52 ` Peter Stuge
2012-06-23 11:59 ` Ciaran McCreesh
2012-06-23 12:16 ` Pacho Ramos
2012-06-23 12:21 ` Ciaran McCreesh
2012-06-23 12:11 ` Pacho Ramos
2012-06-23 12:16 ` Ciaran McCreesh
2012-06-23 12:33 ` Pacho Ramos
2012-06-23 10:37 ` [gentoo-dev] " Duncan
2012-06-23 10:43 ` Duncan
2012-06-23 10:44 ` Ciaran McCreesh
2012-06-23 11:12 ` Rich Freeman
2012-06-23 23:09 ` Duncan
2012-06-21 9:27 ` [gentoo-dev] " Alec Warner
2012-06-21 12:04 ` Rich Freeman
2012-06-23 8:19 ` Pacho Ramos
2012-06-21 11:15 ` Patrick Lauer
2012-06-21 11:37 ` Ciaran McCreesh
2012-06-23 8:01 ` Pacho Ramos
2012-06-21 12:11 ` Homer Parker
2012-06-21 12:30 ` Ciaran McCreesh
2012-06-21 13:13 ` Homer Parker
2012-06-21 13:20 ` Ciaran McCreesh
2012-06-21 20:26 ` Homer Parker
2012-06-21 22:46 ` Rich Freeman
2012-06-29 5:27 ` Mike Frysinger
2012-06-29 5:29 ` Mike Frysinger
2012-06-21 6:41 ` Ciaran McCreesh
2012-06-21 7:24 ` justin
2012-06-21 12:14 ` Homer Parker
2012-06-21 12:38 ` Ciaran McCreesh
2012-06-20 20:39 ` Maxim Kammerer
2012-06-20 20:41 ` Ciaran McCreesh
2012-06-20 20:51 ` Richard Yao
2012-06-29 5:20 ` Mike Frysinger
2012-06-20 20:52 ` Luca Barbato
2012-06-20 21:33 ` Alec Warner
2012-06-21 9:42 ` Ben de Groot
2012-06-29 5:25 ` Mike Frysinger
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=20120623123759.03d19277@googlemail.com \
--to=ciaran.mccreesh@googlemail.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