From: Christoph Mende <angelos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-misc/anki: anki-0.9.9.5.ebuild metadata.xml ChangeLog
Date: Fri, 16 Jan 2009 14:06:49 +0100 [thread overview]
Message-ID: <20090116140649.4f5c1999@gentoo.org> (raw)
In-Reply-To: <200901151438.27409.reavertm@poczta.fm>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On Thu, 15 Jan 2009 14:38:26 +0100
Maciej Mrozowski <reavertm@poczta.fm> wrote:
> That being said, I would rather suggest adding always *precise* and *non-
> general* USE flags descriptions even for global USE flags (actually especially
> for them) as I usually found it pretty much necessary to look up ebuilds to
> get to know what does particular USE flag actually do, and I guess this should
> be avoided at all cost, especially when it does not cost a penny as maintainer
> actually already knows what's all about with those USE flags for particular
> package.
>
That'd definitely be annoying when doing "euse -i <some flag>" and
getting over 9000 hits, so let's remove the "always"
--
Christoph Mende
Gentoo/AMD64 Operational Lead and Release Engineering
GPG: EE2A 454A 6A3B A2D8 E43B FF45 2A19 C3B3 6DA0 C1AF
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-16 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1LNFNu-0004j0-BO@stork.gentoo.org>
2009-01-15 8:12 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-misc/anki: anki-0.9.9.5.ebuild metadata.xml ChangeLog Christian Faulhammer
2009-01-15 13:38 ` Maciej Mrozowski
2009-01-16 13:06 ` Christoph Mende [this message]
2009-01-16 9:18 ` Peter Volkov
2009-01-16 18:20 ` Heath N. Caldwell
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=20090116140649.4f5c1999@gentoo.org \
--to=angelos@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