From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] package.mask-ed ebuilds
Date: Fri, 9 Apr 2010 21:34:35 +0200 [thread overview]
Message-ID: <p2re117dbb91004091234if46d9504scfc40714a4eb091d@mail.gmail.com> (raw)
In-Reply-To: <20100409212204.13f587a2@pomiot.lan>
On 9 April 2010 21:22, Michał Górny <gentoo@mgorny.alt.pl> wrote:
> In my opinion, an ebuild should be added to the tree as long as it will
> be useful to users. If your ebuild is WIP but you want to give some
> users an option to already use it or get some feedback, you could
> consider adding it.
That's what we have overlays for. Move it to the tree once it's ready.
--
Ben de Groot
Gentoo Qt project lead developer
Gentoo Wiki project lead
prev parent reply other threads:[~2010-04-09 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 7:10 [gentoo-dev] package.mask-ed ebuilds Nirbheek Chauhan
2010-04-09 9:53 ` Krzysztof Pawlik
2010-04-09 19:11 ` [gentoo-dev] " Ryan Hill
2010-04-09 19:13 ` [gentoo-dev] " Mark Loeser
2010-04-09 19:22 ` Michał Górny
2010-04-09 19:34 ` Ben de Groot [this message]
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=p2re117dbb91004091234if46d9504scfc40714a4eb091d@mail.gmail.com \
--to=yngwin@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