From: Bastian Ballmann <Crazydj@chaostal.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Tutorial programming with bluez?
Date: Fri, 10 Sep 2004 11:58:10 +0200 [thread overview]
Message-ID: <1094810290.1956.9.camel@espy.crazydj.de> (raw)
In-Reply-To: <517CF7F08A05D4118C380000E869BFA4BDED8B@emg_ntserv2>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
Hi there!
On Fri, 2004-09-10 at 10:02, R.Schade@tu-braunschweig.de wrote:
> I'm looking for a tutorial or an introduction about bluez-programming.
Cause you are from Germany you could try my tutorial located
at http://www.chaostal.de/cgi-bin/parser.cgi?input=article/bluetooth
All other readers could try to learn from the code snippets i
made, but the text is in German!
HTH & Greets
Basti
--
There is no patch for stupidity.
http://www.ccc.de/t-hack/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-10 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 8:02 [Bluez-devel] Tutorial programming with bluez? R.Schade
2004-09-10 9:58 ` Bastian Ballmann [this message]
2004-09-10 13:21 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-09-10 11:34 R.Schade
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=1094810290.1956.9.camel@espy.crazydj.de \
--to=crazydj@chaostal.de \
--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