From: Stephen Crane <steve.crane@rococosoft.com>
To: bluez-announce@lists.sourceforge.net,
bluez-users@lists.sourceforge.net,
bluez-users@lists.sourceforge.net
Cc: marcel@holtmann.org
Subject: New Zaurus packages available
Date: Fri, 04 Jun 2004 10:16:39 +0100 [thread overview]
Message-ID: <1086340599.10892.807.camel@baroque.rococosoft.com> (raw)
Hi,
I have uploaded the following packages to the Sourceforge download site,
http://bluez.sourceforge.net/download/zaurus:
bluez-libs-2.7
bluez-hcidump-1.8
bluez-utils-2.7
bluez-kernel-2.4.18-mh14 --- BlueZ kernel modules for the 3.10 Sharp ROM
Let me know how you get on with them: they haven't been extensively
tested. Also if your favourite util is missing, ask and I might
include it.
Steve
--
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)
next reply other threads:[~2004-06-04 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 9:16 Stephen Crane [this message]
2004-06-05 11:03 ` [Bluez-users] Re: New Zaurus packages available Marcel Holtmann
2004-06-07 5:02 ` [Bluez-users] " Ben Wilson
2004-06-09 9:45 ` Stephen Crane
2004-06-10 4:19 ` Ben Wilson
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=1086340599.10892.807.camel@baroque.rococosoft.com \
--to=steve.crane@rococosoft.com \
--cc=bluez-announce@lists.sourceforge.net \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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