From: TJ OConnor <tjoconno@unity.ncsu.edu>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluetooth 2.1 Spec.
Date: Tue, 24 Jul 2007 12:25:37 -0400 [thread overview]
Message-ID: <C2CBA041.680%tjoconno@unity.ncsu.edu> (raw)
In-Reply-To: <1185294213.3641.136.camel@cookie.hadess.net>
Hello,
Does anyone have access to the Specifications for Bluetooth 2.1? I would
like to get a copy if possible so I can study it further before it is
implemented. Thank you.
TJ
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-07-24 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 23:29 [Bluez-devel] 2 more patches for bluez-gnome Bastien Nocera
2007-07-24 15:42 ` Marcel Holtmann
2007-07-24 16:23 ` Bastien Nocera
2007-07-24 16:25 ` TJ OConnor [this message]
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=C2CBA041.680%tjoconno@unity.ncsu.edu \
--to=tjoconno@unity.ncsu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox