From: Marcel Holtmann <marcel@holtmann.org>
To: Edd Dumbill <edd@usefulinc.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Debian packages updated
Date: Wed, 26 May 2004 19:42:35 +0200 [thread overview]
Message-ID: <1085593355.8896.20.camel@pegasus> (raw)
In-Reply-To: <1085586569.18009.7.camel@saag>
Hi Edd,
> I uploaded new experimental packages for BlueZ 2.7 to Debian
> experimental (expect them there in a week or so, as bluez-cups is NEW),
> and to the http://bluez.sf.net/download/debian/ repository. This build
> has DBUS and CUPS enabled. More details are available in the
> README.Debian file in the bluez-utils package.
>
> Fuller details available on my blog at
> http://usefulinc.com/edd/blog/contents/2004/05/26-bluez/read
>
> I'd welcome feedback from users of the older packages, particularly in
> how the 2.4 -> 2.7 upgrade goes, as the bluez-pan and bluez-sdp packages
> have all been subsumed into bluez-utils.
may you wanna add fixes for two of my stupid mistakes :(
http://cvs.sourceforge.net/viewcvs.py/bluez/libs/include/hci.h?r1=1.35&r2=1.36
http://cvs.sourceforge.net/viewcvs.py/bluez/utils/hidd/main.c?r1=1.3&r2=1.4
Please test these packages and give Edd feedback, so they can move very
soon to unstable.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-05-26 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 15:49 [Bluez-users] Debian packages updated Edd Dumbill
2004-05-26 17:42 ` Marcel Holtmann [this message]
2004-05-26 22:07 ` Achim Bohnet
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=1085593355.8896.20.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=edd@usefulinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.