From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] How shall we name the EAPI 6 patch applying function?
Date: Wed, 3 Apr 2013 15:34:30 -0400 [thread overview]
Message-ID: <CAGfcS_kppawxOv74bQ20tW-5eKmr67eXahP19254-pJXe7ohFA@mail.gmail.com> (raw)
In-Reply-To: <20130403180518.6696ea00@googlemail.com>
On Wed, Apr 3, 2013 at 1:05 PM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Wed, 03 Apr 2013 19:06:31 +0200
> hasufell <hasufell@gentoo.org> wrote:
>> That is not possible without the agreement of the eclass maintainers.
>> So you cannot just "ban" an eclass.
>
> QA certainly can, and should. Or failing that, the Council can step in.
>
No need to have a fight.
If there are reasons not to move everything into the EAPI they should
be discussed. It takes months to implement a new EAPI in general so
the eclass maintainers will be involved I'm sure and everybody can
coordinate nicely.
And the Council already approves all EAPIs, so if for whatever reason
there is a need to make a call they can do so.
There is no need to argue about hypothetical domains of authority.
Let's instead focus on what is the best way to move forward, hope for
consensus, and then deal with disagreement only when that time comes.
Rich
next prev parent reply other threads:[~2013-04-03 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 9:14 [gentoo-dev] How shall we name the EAPI 6 patch applying function? Michał Górny
2013-04-03 9:56 ` Michał Górny
2013-04-03 14:47 ` William Hubbs
2013-04-03 12:33 ` hasufell
2013-04-03 15:29 ` Ciaran McCreesh
2013-04-03 16:56 ` Tomáš Chvátal
2013-04-03 17:35 ` Michał Górny
2013-04-03 17:06 ` hasufell
2013-04-03 17:05 ` Ciaran McCreesh
2013-04-03 19:34 ` Rich Freeman [this message]
2013-04-03 16:36 ` Michał Górny
2013-04-30 4:56 ` [gentoo-dev] " Ryan Hill
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_kppawxOv74bQ20tW-5eKmr67eXahP19254-pJXe7ohFA@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