From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI-3 times and dates
Date: Sun, 31 Jan 2010 14:47:11 +0000 [thread overview]
Message-ID: <82dd739f1001310647p13282512r9250f2b8687dbc38@mail.gmail.com> (raw)
In-Reply-To: <20100122094627.TA4624b.tv@veller.net>
On 22 January 2010 08:58, Torsten Veller <ml-en@veller.net> wrote:
> When can we stabilize EAPI-3 ebuilds?
Note that you can't stick EAPI 3 ebuilds in gentoo-x86, even
package.masked, until the Portage version used to generate the
metadata shipped by rsync supports EAPI 3. Which apparently is not
yet...
--
Ciaran McCreesh
next prev parent reply other threads:[~2010-01-31 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 8:58 [gentoo-dev] EAPI-3 times and dates Torsten Veller
2010-01-22 9:55 ` Petteri Räty
2010-02-23 10:49 ` [gentoo-dev] Who is interested by maintaining gnash ? Romain Perier
2010-01-29 21:43 ` [gentoo-dev] EAPI-3 times and dates Zac Medico
2010-01-29 21:45 ` Jacob Godserv
2010-01-29 21:49 ` Zac Medico
2010-01-31 14:47 ` Ciaran McCreesh [this message]
2010-01-31 17:51 ` Zac Medico
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=82dd739f1001310647p13282512r9250f2b8687dbc38@mail.gmail.com \
--to=ciaran.mccreesh@googlemail.com \
--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