From: Stefan Seyfried <seife@suse.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] dBus
Date: Thu, 4 Jan 2007 16:52:44 +0100 [thread overview]
Message-ID: <20070104155244.GE20707@suse.de> (raw)
In-Reply-To: <20070104132927.94177.qmail@web53311.mail.yahoo.com>
On Thu, Jan 04, 2007 at 09:29:27PM +0800, KS H wrote:
> Hi
> Is that possible disable dBus function in Bluez3.8? =
No.
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
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=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-01-04 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 13:29 [Bluez-users] dBus KS H
2007-01-04 15:52 ` Stefan Seyfried [this message]
2007-01-05 11:30 ` KS H
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=20070104155244.GE20707@suse.de \
--to=seife@suse.de \
--cc=bluez-users@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