From: Marcel Holtmann <marcel@holtmann.org>
To: 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 19:16:22 +0100 [thread overview]
Message-ID: <1193595382.5096.15.camel@aeonflux> (raw)
In-Reply-To: <1193591164.4724c17c545eb@imp.free.fr>
Hi Fabien,
> This is the first patch for what i have in mind for the dbus errors management:
> - org.bluez.Error.xxx : generic errors used by hcid and all services, declared
> in common-error.h
> - org.bluez.Error.SERVICENAME.yyy : errors that have a meaning only to a local
> service.
> - org.bluez.core.Error.zzz : errors that have a meaning local to hcid, not
> shared with other services.
I like to have org.bluez.Error only. There is no need to get an extra
hierarchy level.
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 18:16 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 [this message]
2007-10-28 18:01 ` fabchevalier
2007-10-28 18:15 ` fabchevalier
2007-10-28 19:40 ` Marcel Holtmann
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=1193595382.5096.15.camel@aeonflux \
--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