From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] current Bluez document describing
Date: Mon, 26 Feb 2007 00:47:27 +0100 [thread overview]
Message-ID: <1172447247.20450.9.camel@violet> (raw)
In-Reply-To: <200702251110.07289.penguinacity@yahoo.com>
Hi Walt,
> There is a lot of outdated doc out there for this. It has even been admitted
> here.
> What is the current sanctioned webpage or document that describes it?
BlueZ itself changed quite a lot in the last two years. Feel free to use
wiki.bluez.org to create some state of the art documentation.
> or what does rfcomm do and how
> what is the device named in rfcomm.conf? (the dongle?)
> Maybe the comment might say that if it is.
> Saying 'the device' is rather obtuse.
No idea what's your question. Be more specific.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-02-25 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 16:10 [Bluez-users] current Bluez document describing penguinacity
2007-02-25 23:47 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-27 20:16 [Bluez-users] pairing from bluez Choi Sonim
2007-02-27 20:50 ` [Bluez-users] current Bluez document describing walt shekrota
2007-02-27 22:56 ` Timur Alperovich
2007-02-28 14:09 ` walt shekrota
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=1172447247.20450.9.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-users@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.