From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] why is '@' allowed in use flags
Date: Mon, 7 Jun 2010 08:33:48 +0100 [thread overview]
Message-ID: <20100607083348.0fdd8c4a@snowcone> (raw)
In-Reply-To: <20100607072946.GG6316@hrair>
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
On Mon, 7 Jun 2010 00:29:46 -0700
Brian Harring <ferringb@gmail.com> wrote:
> Follow up discussion point; anyone got a character to use for
> seperating use_expand groups and their members? I'm well aware '_'
> is used right now, but it's use is nonoptimal- the only way to break
> down a use_expanded target in IUSE is to know the use_expand
> grouppings themselves, which is profile defined... a flaw I've hated
> since day one.
We've been using : in exheres-0.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-06-07 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 5:23 [gentoo-pms] why is '@' allowed in use flags Brian Harring
2010-06-07 7:26 ` Ciaran McCreesh
2010-06-07 7:29 ` Brian Harring
2010-06-07 7:33 ` Ciaran McCreesh [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=20100607083348.0fdd8c4a@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-pms@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