From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Simple typo fix for bluez-utils
Date: Tue, 06 Mar 2007 12:43:32 +0000 [thread overview]
Message-ID: <1173185012.10237.7.camel@cookie.hadess.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 55 bytes --]
Patch attached
--
Bastien Nocera <hadess@hadess.net>
[-- Attachment #2: bluez-utils-typo.patch --]
[-- Type: text/x-patch, Size: 716 bytes --]
Index: hcid/dbus-api.txt
===================================================================
RCS file: /cvsroot/bluez/utils/hcid/dbus-api.txt,v
retrieving revision 1.107
diff -u -p -r1.107 dbus-api.txt
--- hcid/dbus-api.txt 5 Mar 2007 14:43:04 -0000 1.107
+++ hcid/dbus-api.txt 6 Mar 2007 12:45:26 -0000
@@ -827,7 +827,7 @@ Methods string GetAddress()
includes an inquiry procedure and remote device name
resolving.
- On start up this process will generate a DiscoveryStart
+ On start up this process will generate a DiscoveryStarted
signal and then return RemoteDeviceFound and also
RemoteNameUpdated signals. If the procedure has been
finished an DiscoveryCompleted signal will be sent.
[-- 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-03-06 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 12:43 Bastien Nocera [this message]
2007-03-06 14:38 ` [Bluez-devel] Simple typo fix for bluez-utils 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=1173185012.10237.7.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--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