From: Szymon Janc <szymon.janc@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Szymon Janc <szymon.janc@gmail.com>
Subject: [PATCH 5/5] rfcomm: Remove bogus manual entry
Date: Fri, 31 May 2013 00:01:57 +0200 [thread overview]
Message-ID: <1369951317-16789-5-git-send-email-szymon.janc@gmail.com> (raw)
In-Reply-To: <1369951317-16789-1-git-send-email-szymon.janc@gmail.com>
This was introduced in commit b1b5f09d40 "Include security parameters"
back in 2007. Those options are already descibed few lines below.
---
tools/rfcomm.1 | 17 +++--------------
1 file changed, 3 insertions(+), 14 deletions(-)
diff --git a/tools/rfcomm.1 b/tools/rfcomm.1
index 51df284..a108609 100644
--- a/tools/rfcomm.1
+++ b/tools/rfcomm.1
@@ -49,20 +49,9 @@ Prints information about all configured RFCOMM devices.
Switch TTY into raw mode (doesn't work with "bind").
.TP
.BI -i " <hciX> | <bdaddr>"
-The command is applied to device
-.BI -A
-Enable authentication.
-.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
-device. If not specified, the command will be use the first
-available Bluetooth device.
+The command is applied to device hciX, which must be the name or the address of
+an installed Bluetooth device. If not specified, the command will be use the
+first available Bluetooth device.
.TP
.BI -A
Enable authentification
--
1.7.10.4
next prev parent reply other threads:[~2013-05-30 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 22:01 [PATCH 1/5] core: Add option to list available plugins Szymon Janc
2013-05-30 22:01 ` [PATCH 2/5] man: Update bluetoothd manual Szymon Janc
2013-05-31 20:40 ` [PATCH v2 " Szymon Janc
2013-06-13 13:20 ` Johan Hedberg
2013-05-30 22:01 ` [PATCH 3/5] build: Fix generating bluetoothd manpage Szymon Janc
2013-05-30 22:01 ` [PATCH 4/5] tools: Update rfcomm help Szymon Janc
2013-05-30 22:01 ` Szymon Janc [this message]
2013-05-30 22:13 ` [PATCH 1/5] core: Add option to list available plugins 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=1369951317-16789-5-git-send-email-szymon.janc@gmail.com \
--to=szymon.janc@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).