From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] dbus.c cleanup
Date: Mon, 31 Oct 2005 13:12:06 +0100 [thread overview]
Message-ID: <1130760726.17124.17.camel@blade> (raw)
In-Reply-To: <e1effdeb0510310359g33724820y596b244076d08315@mail.gmail.com>
Hi Claudio,
> I don't have cleanup patches to be sent. A new release can be good to
> receive the users/developers feedback.
I have to do some other small fixes in other parts of bluez-utils, but
the release is actually planned for today.
> Some cleanups/improvements suggestions for the next release:
> - find_conn is a shared function: put in a shared directory. It's used
> by hcitool.c and dbus.c
I know, but this has time. Maybe you wanna move it into lib.c inside the
hcid directory first.
> - Disconnect signal: handle de disconnect signal sent when the
> dbus-daemon exits.
I have no idea what that means.
> - split dbus.c file:
> - use session bus to send the PinRequest message: using the session
> bus it's possible start the dbus pin helper application automatically
This sounds like a good idea. Is anybody working on it? However the
bluez-pin package needs to updated to support the latest D-Bus version,
because we don't support the D-Bus 0.23 anymore.
> I think Eduardo is working on some services device configuration
> services. Maybe it should be better wait his patch. I will ask him and
> confirm soon.
There is plenty of time after the release. I don't consider the current
D-Bus API as stable.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-10-31 12:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 17:53 [Bluez-devel] [PATCH] dbus.c cleanup Johan Hedberg
2005-10-29 18:07 ` Marcel Holtmann
2005-10-29 18:48 ` Johan Hedberg
2005-10-29 19:07 ` Marcel Holtmann
2005-10-31 11:59 ` Claudio Takahasi
2005-10-31 12:07 ` Johan Hedberg
2005-10-31 12:14 ` Marcel Holtmann
2005-10-31 12:30 ` Eduardo Rocha
2005-10-31 12:12 ` Marcel Holtmann [this message]
2005-10-31 13:47 ` Claudio Takahasi
2005-11-01 13:11 ` Marcel Holtmann
2005-11-01 13:21 ` Claudio Takahasi
2005-11-01 19:08 ` Claudio Takahasi
2005-11-01 19:58 ` Marcel Holtmann
2005-11-01 20:23 ` Johan Hedberg
2005-11-01 20:40 ` Marcel Holtmann
2005-11-01 20:53 ` Claudio Takahasi
-- strict thread matches above, loose matches on Subject: below --
2005-11-03 7:20 Johan Hedberg
2005-11-03 8:34 ` Marcel Holtmann
2005-11-03 8:54 ` Johan Hedberg
2005-11-03 9:08 ` Marcel Holtmann
2005-11-03 9:23 ` Johan Hedberg
2005-11-03 9:41 ` Marcel Holtmann
2005-11-03 10:13 ` Johan Hedberg
2005-11-03 10:33 ` Marcel Holtmann
2005-11-03 14:22 ` Johan Hedberg
2005-11-03 14:36 ` 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=1130760726.17124.17.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