From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [BlueZ-Announce] Release of bluez-hcidump-1.38
Date: Fri, 27 Jul 2007 21:03:38 +0200 [thread overview]
Message-ID: <1185563018.13228.34.camel@violet> (raw)
In-Reply-To: <1185561401.2848.52.camel@cookie.hadess.net>
Hi Bastien,
> > I released a new version of the hcidump package. This version adds
> > support for daemon mode that allows to access HCI protocol traffic over
> > the network.
> >
> > The sources can be found at http://www.bluez.org/download.html
>
> When people package the next version of bluez-gnome, should they make it
> have a dependency on that version of bluez-hcidump, to get the analyser
> working?
no. The analyzer works perfectly fine without hcidump. It can still read
binary trace files. It is only an extra option for people that do want
live import.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-07-27 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1185560447.13228.28.camel@violet>
2007-07-27 18:36 ` [Bluez-devel] [BlueZ-Announce] Release of bluez-hcidump-1.38 Bastien Nocera
2007-07-27 19:03 ` 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=1185563018.13228.34.camel@violet \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.