From: "Frédéric DALLEAU" <frederic.dalleau@access-company.com>
To: bluez development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] [patch] updates rfcomm man page
Date: Wed, 21 Feb 2007 17:11:01 +0100 [thread overview]
Message-ID: <45DC6F15.8010908@access-company.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 95 bytes --]
This patch updates rfcomm man page!
--
Frederic
Without the wind, the grass does not move.
[-- Attachment #2: rfcomm-man.patch --]
[-- Type: text/x-patch, Size: 610 bytes --]
? rfcomm/Makefile.in
? rfcomm/cvs
Index: rfcomm/rfcomm.1
===================================================================
RCS file: /cvsroot/bluez/utils/rfcomm/rfcomm.1,v
retrieving revision 1.6
diff -u -r1.6 rfcomm.1
--- rfcomm/rfcomm.1 24 Dec 2006 13:49:04 -0000 1.6
+++ rfcomm/rfcomm.1 21 Feb 2007 16:10:30 -0000
@@ -53,6 +53,14 @@
.TP
.BI -i " <hciX> | <bdaddr>"
The command is applied to device
+.BI -A
+Enable authentification
+.BI -E
+Enable encryption
+.BI -S
+Secure connection
+.BI -M
+Become the master of a piconet
.I
hciX
, which must be the name or the address of an installed Bluetooth
[-- Attachment #3: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-02-21 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 16:11 Frédéric DALLEAU [this message]
2007-02-21 19:45 ` [Bluez-devel] [patch] updates rfcomm man page 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=45DC6F15.8010908@access-company.com \
--to=frederic.dalleau@access-company.com \
--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