From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Some thoughts on the current D-BUS interface
Date: Tue, 01 Nov 2005 20:53:55 +0100 [thread overview]
Message-ID: <1130874835.5048.12.camel@blade> (raw)
In-Reply-To: <3013cac80511011105y2be7647bi4fb0994efd6f8a31@mail.gmail.com>
Hi Eduardo,
> here is the device Up and Down dbus methods.
the patch is in the CVS now. However I am not sure about the future of
any of these two methods. Do we really want the possibility to up and
down a Bluetooth adapter?
For the test scripts, make sure that you include "#!/usr/bin/python" on
the first line and I basically like one or two bigger test scripts. An
extra script for every method is overkill.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-01 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 22:40 [Bluez-devel] Some thoughts on the current D-BUS interface Johan Hedberg
2005-10-31 23:05 ` Marcel Holtmann
2005-10-31 23:36 ` Johan Hedberg
2005-11-01 12:33 ` Claudio Takahasi
2005-11-01 15:54 ` Johan Hedberg
2005-11-01 16:46 ` Marcel Holtmann
2005-11-01 19:05 ` Eduardo Rocha
2005-11-01 19:53 ` Marcel Holtmann [this message]
2005-11-01 20:27 ` Johan Hedberg
2005-11-02 6:32 ` Ville Tervo
2005-11-01 19:48 ` Johan Hedberg
2005-11-02 9:51 ` Johan Hedberg
2005-11-02 11:18 ` Johan Hedberg
2005-11-02 14:25 ` 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=1130874835.5048.12.camel@blade \
--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;
as well as URLs for NNTP newsgroup(s).