From: Philip Blundell <pb@nexus.co.uk>
To: David Woodhouse <dwmw2@redhat.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] patch for d-bus support in hcid
Date: 24 Jun 2003 10:31:33 +0100 [thread overview]
Message-ID: <1056447092.10483.21.camel@mill.nexus.co.uk> (raw)
In-Reply-To: <1056446930.29264.403.camel@passion.cambridge.redhat.com>
On Tue, 2003-06-24 at 10:28, David Woodhouse wrote:
> Thanks for doing this. There are now packages in Red Hat Rawhide with
> this enabled.... volunteers to provide the GNOME and KDE GUI side for
> this welcomed...
Great. I made a GTK-based GUI for use in GPE; it should work fine in a
desktop environment too.
ftp://ftp.handhelds.org/pub/projects/gpe/source/bluez-pin-0.20.tar.gz
p.
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-06-24 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 16:42 [Bluez-devel] patch for d-bus support in hcid Philip Blundell
2003-06-20 16:19 ` David Woodhouse
2003-06-21 0:13 ` Max Krasnyansky
2003-06-24 14:00 ` Version 3 libs/utils (was: Re: [Bluez-devel] patch for d-bus support in hcid) Stephen Crane
2003-06-24 17:31 ` Max Krasnyansky
2003-06-25 9:17 ` Stephen Crane
2003-06-25 12:15 ` Marcel Holtmann
2003-06-26 17:15 ` Version 3 libs/utils Max Krasnyansky
2003-07-23 8:12 ` Version 3 libs/utils (was: Re: [Bluez-devel] patch for d-bus support in hcid) Paul Hedderly
2003-06-24 9:28 ` [Bluez-devel] patch for d-bus support in hcid David Woodhouse
2003-06-24 9:31 ` Philip Blundell [this message]
2003-09-04 21:18 ` David Woodhouse
2003-09-04 22:33 ` Philip Blundell
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=1056447092.10483.21.camel@mill.nexus.co.uk \
--to=pb@nexus.co.uk \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dwmw2@redhat.com \
/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