From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Looking for a Palm with Bluetooth
Date: Sun, 21 Aug 2005 10:48:03 +0200 [thread overview]
Message-ID: <1124614083.7598.0.camel@notepaq> (raw)
In-Reply-To: <1124468847.1783.4.camel@panic>
Hi Collin,
> Could you tell us the secret UUIDs?
look at the sdptool source code in the CVS.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-08-21 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 16:03 [Bluez-devel] Looking for a Palm with Bluetooth Marcel Holtmann
2005-08-19 16:17 ` Nicholas Piper
2005-08-21 13:26 ` Marcel Holtmann
2005-08-19 16:27 ` Collin R. Mulliner
2005-08-21 8:48 ` Marcel Holtmann [this message]
2005-08-20 3:57 ` Tom Allebrandi
2005-08-21 8:51 ` Marcel Holtmann
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=1124614083.7598.0.camel@notepaq \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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.