From: Stefan Seyfried <seife@suse.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [patch] make apitest more useful
Date: Fri, 7 Mar 2008 16:06:55 +0100 [thread overview]
Message-ID: <20080307150655.GB11011@suse.de> (raw)
In-Reply-To: <1204899369.28006.2.camel@californication>
Hi Marcel,
On Fri, Mar 07, 2008 at 03:16:09PM +0100, Marcel Holtmann wrote:
> the apitest is really only a test program,
I know :-)
It is still useful to hand out to people for debugging their setup.
As it is much more low level than bluez-gnome and kdebluetooth, it
is easier to tell a bug reporter *exactly* what to do with apitest
than with the grapical tools. That's why i bothered fixing that issue.
> but I applied the patch neverless.
Thanks. It now actually allows to test "DiscoverDevices" which is much
more useful, even as testing tool only ;-)
-- =
Stefan Seyfried
R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-03-07 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 18:48 [Bluez-devel] [patch] make apitest more useful Stefan Seyfried
2008-03-07 14:16 ` Marcel Holtmann
2008-03-07 15:06 ` Stefan Seyfried [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=20080307150655.GB11011@suse.de \
--to=seife@suse.de \
--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