From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Eclass vs EAPI For Utility Functions (Patching/etc)
Date: Thu, 19 Jun 2014 13:53:51 -0400 [thread overview]
Message-ID: <CAGfcS_kHZCJr8UBmkVS7_d6a_BFyVN1JwFZaUWFK2Cv08_p7UA@mail.gmail.com> (raw)
In-Reply-To: <20140619170311.GA11784@linux1>
On Thu, Jun 19, 2014 at 1:03 PM, William Hubbs <williamh@gentoo.org> wrote:
> Hi all:
>
> I am strongly in favor of the eapi-based approach as well, for all of
> the reasons mentioned in the thread so far.
Good thing your proxy got it right then! :)
http://www.gentoo.org/proj/en/council/meeting-logs/20140617-summary.txt
Rich
prev parent reply other threads:[~2014-06-19 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 11:00 [gentoo-dev] Eclass vs EAPI For Utility Functions (Patching/etc) Rich Freeman
2014-06-15 12:14 ` Ciaran McCreesh
2014-06-15 13:30 ` Michał Górny
2014-06-19 22:05 ` [gentoo-dev] " Steven J. Long
2014-06-19 22:22 ` Rich Freeman
2014-06-15 23:36 ` [gentoo-dev] Auto-patching ebuilds themselves Was: " Duncan
2014-06-16 9:54 ` [gentoo-dev] " Pacho Ramos
2014-06-19 17:03 ` William Hubbs
2014-06-19 17:53 ` 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_kHZCJr8UBmkVS7_d6a_BFyVN1JwFZaUWFK2Cv08_p7UA@mail.gmail.com \
--to=rich0@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