From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Calling die in a subshell
Date: Sat, 15 Jun 2013 17:50:05 +0100 [thread overview]
Message-ID: <20130615175005.156a97e9@googlemail.com> (raw)
In-Reply-To: <51BC9A11.2030804@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 15 Jun 2013 18:45:05 +0200
hasufell <hasufell@gentoo.org> wrote:
> On 06/15/2013 06:43 PM, Ciaran McCreesh wrote:
> > On Sat, 15 Jun 2013 18:41:18 +0200 hasufell <hasufell@gentoo.org>
> > wrote:
> >> On 06/15/2013 06:24 PM, Tom Wijsman wrote:
> >>> Why not fix the specs?
> >
> >> from council log
> >> http://www.gentoo.org/proj/en/council/meeting-logs/20120911.txt
> >
> >> <Chainsaw> Okay for EAPI 5. *Nothing* gets applied
> >> retroactively. *EVER*
> >
> >> So that means some people think it doesn't even matter what the
> >> issue is. We never fix the spec, we just enhance it.
> >
> >> Oh, you asked for reasoning...
> >
> > If you want the reasoning for that decision, you should look at
> > the entire log, and not just one line of it.
> >
> >
>
> I was not talking about that decision. Stop derailing threads on -dev.
Then I appear to have misunderstood what you wanted reasoning for.
Please explain further. Chances are I can give you an answer, since
I've been involved in most of the policy-related discussions for EAPIs
and PMS.
- --
Ciaran McCreesh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iEYEARECAAYFAlG8m0IACgkQ96zL6DUtXhETyACg0WVMQ4QslQezKtzOCpo+gGys
tNsAoLq4a15J0hhNG657HvLckBXw++f3
=+LFr
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-06-15 16:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 16:06 [gentoo-dev] Calling die in a subshell Mike Gilbert
2013-06-15 16:14 ` Diego Elio Pettenò
2013-06-15 16:16 ` Ulrich Mueller
2013-06-15 16:19 ` hasufell
2013-06-15 16:21 ` Diego Elio Pettenò
2013-06-15 16:25 ` Ulrich Mueller
2013-06-15 17:41 ` Michał Górny
2013-06-16 13:00 ` Ulrich Mueller
2013-06-15 16:22 ` Mike Gilbert
2013-06-15 16:24 ` Tom Wijsman
2013-06-15 16:41 ` hasufell
2013-06-15 16:43 ` Ciaran McCreesh
2013-06-15 16:45 ` hasufell
2013-06-15 16:50 ` Ciaran McCreesh [this message]
2013-06-15 16:42 ` Ciaran McCreesh
2013-06-15 16:56 ` Mike Gilbert
2013-06-15 16:58 ` hasufell
2013-06-15 17:01 ` Ciaran McCreesh
2013-06-15 17:02 ` Mike Gilbert
2013-06-17 20:10 ` vivo75
2013-06-17 20:49 ` Mike Gilbert
2013-06-18 7:06 ` [gentoo-dev] " Duncan
2013-06-19 2:01 ` vivo75
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=20130615175005.156a97e9@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