From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 2011-11-08
Date: Mon, 31 Oct 2011 11:27:57 +0100 [thread overview]
Message-ID: <20142.30765.50483.870591@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <4EAE6FD8.5030203@gentoo.org>
>>>>> On Mon, 31 Oct 2011, Petteri Räty wrote:
> Let's vote on if you are allowed to remove functions from eclasses (or
> break the API in general):
> http://archives.gentoo.org/gentoo-dev/msg_f797a983b0d11677a1f781e48ab4e97d.xml
> Last time this came up a decision wasn't reached:
> http://www.gentoo.org/proj/en/council/meeting-logs/20100726-summary.txt
> The decision should then be documented here:
> http://devmanual.gentoo.org/eclass-writing/index.html
Why do we need a decision here? Isn't it simply a special case of the
"adding and updating eclasses" policy?
Ulrich
next prev parent reply other threads:[~2011-10-31 10:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 16:30 [gentoo-project] Call for agenda items -- Council meeting 2011-11-08 Fabian Groffen
2011-10-26 16:35 ` [gentoo-project] Re: [gentoo-dev] " Michał Górny
2011-10-26 16:37 ` Fabian Groffen
2011-10-26 16:49 ` Michał Górny
2011-10-26 17:06 ` Fabian Groffen
2011-10-26 17:11 ` Michał Górny
2011-10-26 17:15 ` Fabian Groffen
[not found] ` <1319652305.5300.7.camel@belkin4>
2011-10-26 19:09 ` Matt Turner
2011-10-26 20:58 ` Fabian Groffen
2011-10-26 21:03 ` Chí-Thanh Christopher Nguyễn
2011-10-26 21:07 ` Fabian Groffen
2011-10-26 22:13 ` Chí-Thanh Christopher Nguyễn
2011-10-27 7:08 ` Fabian Groffen
2011-10-26 16:50 ` Markos Chandras
2011-10-31 6:43 ` Peter Volkov
2011-10-31 8:14 ` Michał Górny
2011-10-31 8:27 ` Peter Volkov
2011-10-31 9:52 ` [gentoo-project] " Petteri Räty
2011-10-31 10:27 ` Ulrich Mueller [this message]
2011-11-01 21:07 ` Petteri Räty
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=20142.30765.50483.870591@a1i15.kph.uni-mainz.de \
--to=ulm@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