From: Johan Hedberg <johan.hedberg@gmail.com>
To: Burt Silverman <burtms@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Print an error message if g_dbus_setup_bus fails.
Date: Tue, 30 Aug 2011 13:13:30 +0300 [thread overview]
Message-ID: <20110830101330.GA20724@dell> (raw)
In-Reply-To: <1314398341-2733-1-git-send-email-burtms@gmail.com>
Hi Burt,
On Fri, Aug 26, 2011, Burt Silverman wrote:
> That is standard processing when dbus_error_is_set() returns true, according to
> dbus/dbus/dbus-errors.c.
> In this case of g_dbus_setup_bus(), it provides extra help for determing the
> specific cause of the error.
> ---
> src/main.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
Applied (after I made the message prefix a bit more descriptive).
Thanks.
Johan
next prev parent reply other threads:[~2011-08-30 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 22:39 [PATCH] Print an error message if g_dbus_setup_bus fails Burt Silverman
2011-08-30 10:13 ` Johan Hedberg [this message]
2011-09-08 15:09 ` Burt Silverman
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=20110830101330.GA20724@dell \
--to=johan.hedberg@gmail.com \
--cc=burtms@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).