From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] dbus pin failure
Date: Mon, 06 Mar 2006 18:34:31 +0100 [thread overview]
Message-ID: <1141666471.4733.3.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <1141663646.4110.60.camel@pmac.infradead.org>
Hi David,
> > ok then maybe it is too new. Does bluez-pin or hcid create this error
> > message? I am still at 0.60 on all of my machines.
>
> It's printed by bluez-pin
so I assume this means that bluez-pin is at fault. Actually that is out
of my responsibility. However you also should already have patches in it
for making it work with 0.36. Maybe these need to be reviewed.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-03-06 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 14:30 [Bluez-devel] dbus pin failure David Woodhouse
2006-03-03 14:59 ` Marcel Holtmann
2006-03-03 20:34 ` David Woodhouse
2006-03-05 4:22 ` Marcel Holtmann
2006-03-06 16:47 ` David Woodhouse
2006-03-06 17:34 ` Marcel Holtmann [this message]
2006-03-06 22:26 ` David Woodhouse
2006-03-06 22:35 ` Marcel Holtmann
2006-03-07 15:03 ` Claudio Takahasi
2006-03-14 17:00 ` David Woodhouse
2006-03-14 17:07 ` 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=1141666471.4733.3.camel@aeonflux.holtmann.net \
--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