From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Adding two USE flags to 2008.0's profiles
Date: Sun, 03 Feb 2008 03:14:51 +0200 [thread overview]
Message-ID: <47A5158B.50601@gentoo.org> (raw)
In-Reply-To: <1201956114.14162.39.camel@inertia.twi-31o2.org>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
Chris Gianelloni kirjoitti:
>
> Understandable, bluetooth isn't the most mature thing in Linux. It
> tends to either work or it doesn't.
>
Actually bluetooth support is in quite a good shape. The thing was there
was a urgent need to get bluez-utils-3* stable for which I need some doc
updates etc before it can go stable. (Yes I am a slacker there)
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2008-02-03 1:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 6:42 [gentoo-dev] [RFC] Adding two USE flags to 2008.0's profiles Chris Gianelloni
2008-02-02 8:45 ` [gentoo-dev] " Christian Faulhammer
2008-02-02 12:41 ` Chris Gianelloni
2008-02-03 1:14 ` Petteri Räty [this message]
2008-02-03 7:41 ` Josh Saddler
2008-02-02 13:50 ` [gentoo-dev] " Brent Baude
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=47A5158B.50601@gentoo.org \
--to=betelgeuse@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