From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Make inotify a global USE flag?
Date: Thu, 21 Mar 2013 15:14:17 +0100 [thread overview]
Message-ID: <20811.5561.731803.953862@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <514AF38E.60600@plaimi.net>
>>>>> On Thu, 21 Mar 2013, Alexander Berntsen wrote:
>> BTW, half of the local flag descriptions are "Enable inotify
>> support". Imagine that! ;-)
> Why not just make it "Enable inotify support", and write more
> detailed local flags?
The point is that this so-called description adds no useful
information whatsoever. Most of the time USE="foo" will enable some
"foo" feature.
Ulrich
next prev parent reply other threads:[~2013-03-21 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 10:29 [gentoo-dev] Make inotify a global USE flag? Ulrich Mueller
2013-03-21 10:32 ` Samuli Suominen
2013-03-21 11:43 ` Peter Stuge
2013-03-21 12:02 ` Samuli Suominen
2013-03-21 12:10 ` Peter Stuge
2013-03-21 12:19 ` Sergey Popov
2013-03-21 12:26 ` Samuli Suominen
2013-03-21 13:33 ` Peter Stuge
2013-03-21 14:30 ` Tom Wijsman
2013-03-21 16:32 ` Michał Górny
2013-03-21 11:48 ` Alexander Berntsen
2013-03-21 14:14 ` Ulrich Mueller [this message]
2013-03-21 16:14 ` Alexander Berntsen
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=20811.5561.731803.953862@a1i15.kph.uni-mainz.de \
--to=ulm@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