From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: ccc.eclass
Date: Sat, 16 Jan 2010 15:29:48 +0200 [thread overview]
Message-ID: <4B51BF4C.7070807@gentoo.org> (raw)
In-Reply-To: <20100111222315.GA6656@hrair>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On 01/12/2010 12:23 AM, Brian Harring wrote:
> On Mon, Jan 11, 2010 at 09:25:51PM +0100, Raaal Porcel wrote:
>> scarabeus told me that the eclass can't be removed until two years since
>> the deprecation date, so...
>>
>> Removal of the eclass on 2012/01/11
>
> Reasoning? Prior to env saving we couldn't particularly punt
> eclasses, but env saving is widely deployed now...
>
> ~harring
At least my argument at the time was that better to be safe when the
benefit from removing old eclasses isn't that much.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2010-01-16 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 18:02 [gentoo-dev] Last rites: ccc.eclass Raúl Porcel
2010-01-11 20:25 ` Raúl Porcel
2010-01-11 22:23 ` Brian Harring
2010-01-11 23:15 ` Tomáš Chvátal
2010-01-16 13:29 ` Petteri Räty [this message]
2010-01-26 7:17 ` [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=4B51BF4C.7070807@gentoo.org \
--to=betelgeuse@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