From: ligi <ligi@egabriel.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Documentation for development
Date: Thu, 21 Apr 2005 15:21:32 +0200 [thread overview]
Message-ID: <4267A8DC.9060805@egabriel.de> (raw)
In-Reply-To: <200504201931.06626.alan@mizrahi.com.ve>
>Is there any documentation I can read about bluetooth development?
>
>
>
http://www.benhui.net/modules.php?name=Bluetooth
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-21 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 2:37 [Bluez-devel] Documentation for development Alan Mizrahi
2005-04-20 3:04 ` gao.yingbin
2005-04-20 9:29 ` Marcel Holtmann
2005-04-20 23:31 ` Alan Mizrahi
2005-04-20 23:48 ` Marcel Holtmann
2005-04-21 13:21 ` ligi [this message]
2005-04-22 6:56 ` Albert Huang
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=4267A8DC.9060805@egabriel.de \
--to=ligi@egabriel.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;
as well as URLs for NNTP newsgroup(s).