From: Hans de Graaff <graaff@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: ruby-ng.eclass - new eclass for ruby-based packages
Date: Sat, 05 Dec 2009 09:59:59 +0100 [thread overview]
Message-ID: <1260003599.8760.4.camel@localhost> (raw)
In-Reply-To: <20091202104632.GA5853@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
On Wed, 2009-12-02 at 11:46 +0100, Fabian Groffen wrote:
> I guess you better add a section for known eapis that are too old to
> your liking, and use the *) section for an oops message saying you don't
> know about ${EAPI} yet, and to please file a bug.
Yes, good idea. We've gone with this solution.
Kind regards,
Hans
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-05 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 7:11 [gentoo-dev] RFC: ruby-ng.eclass - new eclass for ruby-based packages Hans de Graaff
2009-12-02 8:51 ` [gentoo-dev] " Christian Faulhammer
2009-12-02 8:57 ` Tomáš Chvátal
2009-12-02 10:46 ` Fabian Groffen
2009-12-05 8:59 ` Hans de Graaff [this message]
2009-12-02 10:59 ` Christian Faulhammer
2009-12-05 9:32 ` Hans de Graaff
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=1260003599.8760.4.camel@localhost \
--to=graaff@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