From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] typo in dbus-test python script
Date: Sat, 29 Jul 2006 14:54:50 +0200 [thread overview]
Message-ID: <1154177690.25939.10.camel@localhost> (raw)
In-Reply-To: <87zmeuq6iw.fsf@phugues.par.afp.com>
Hi Hugues,
> Just in case you did'nt notice, there is apparently a typo in the
> dbus-test python script in the CVS repository.
>
> Index: hcid/dbus-test
> ===================================================================
> RCS file: /cvsroot/bluez/utils/hcid/dbus-test,v
> retrieving revision 1.20
> diff -u -r1.20 dbus-test
> --- hcid/dbus-test 26 Jun 2006 12:33:13 -0000 1.20
> +++ hcid/dbus-test 28 Jul 2006 12:01:58 -0000
> @@ -186,7 +186,7 @@
> @dbus.decorators.explicitly_pass_message
> def mgr_signal_handler(*args, **keywords):
> dbus_message = keywords["dbus_message"]
> - print '%s: ' % dbus_messsage.get_member()
> + print '%s: ' % dbus_message.get_member()
> for arg in args[1:]:
> print '%s ' % arg,
> print
you are right. Thanks for pointing this out. It is fixed in the CVS now.
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-07-29 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 12:05 [Bluez-devel] typo in dbus-test python script Hugues Lafarge
2006-07-29 12:54 ` Marcel Holtmann [this message]
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=1154177690.25939.10.camel@localhost \
--to=marcel@holtmann.org \
--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