From: Marcel Holtmann <marcel@holtmann.org>
To: fabchevalier@free.fr
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH 1/3] move common exceptions to common/ directory
Date: Sun, 28 Oct 2007 20:40:24 +0100 [thread overview]
Message-ID: <1193600424.4516.1.camel@aeonflux> (raw)
In-Reply-To: <1193595313.4724d1b17e3bf@imp.free.fr>
Hi Fabien,
> > I like to have org.bluez.Error only. There is no need to get an extra
> > hierarchy level.
> >
>
> That's basically how things are today... however if have no objection if you
> want to change that...
it is this way, because it was the easiest way. I want one
org.bluez.Error to handle all error cases.
> Btw did you have a look at the send_message_and_unref ==>
> dbus_connection_send_and_unref patch ? Is it ok for you ? (Aven't tested but i
> think those three patches may depend on it)
Not really. I leave this to Johan, since he worked on most of common/
stuff.
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
next prev parent reply other threads:[~2007-10-28 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 17:06 [Bluez-devel] [PATCH 1/3] move common exceptions to common/ directory fabchevalier
2007-10-28 18:16 ` Marcel Holtmann
2007-10-28 18:01 ` fabchevalier
2007-10-28 18:15 ` fabchevalier
2007-10-28 19:40 ` Marcel Holtmann [this message]
2007-10-28 19:06 ` fabchevalier
2007-10-28 20:46 ` 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=1193600424.4516.1.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=fabchevalier@free.fr \
/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