From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: Council Meeting Scheduled for 17 Jun 2014 at 19:00 UTC
Date: Fri, 13 Jun 2014 09:48:30 -0400 [thread overview]
Message-ID: <CAGfcS_kGY-0=g3XaOLrtnQ2VzgL_YNOnZHE-oFiP8_12qGQjMw@mail.gmail.com> (raw)
In-Reply-To: <21402.51565.346627.455570@a1i15.kph.uni-mainz.de>
On Fri, Jun 13, 2014 at 5:50 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
>
> For the case that we accept 4b "User patches" and 4a "Patch applying
> function in package manager", I wonder if we shouldn't re-take the
> vote on 1d "PATCHES support in default src_prepare" (which was a tie).
Makes sense.
I think the real objection isn't to those particular EAPI features,
but rather a philosophical debate over what belongs in EAPI vs what
belongs in eclasses. I already put in my two cents on -dev on that
one.
Rich
prev parent reply other threads:[~2014-06-13 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGfcS_=7s2Typ2kqHskZ4vqsSS_H4G24Xd_x+4N1sUFg-t6ZtA@mail.gmail.com>
2014-06-13 9:50 ` [gentoo-project] Re: Council Meeting Scheduled for 17 Jun 2014 at 19:00 UTC Ulrich Mueller
2014-06-13 9:57 ` Michał Górny
2014-06-13 10:16 ` Ulrich Mueller
2014-06-13 13:48 ` Rich Freeman [this message]
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='CAGfcS_kGY-0=g3XaOLrtnQ2VzgL_YNOnZHE-oFiP8_12qGQjMw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-project@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