From: Johan Hedberg <johan.hedberg@gmail.com>
To: Slawomir Bochenski <lkslawek@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH obexd] Simplify counting new missed calls
Date: Tue, 27 Sep 2011 12:37:43 +0300 [thread overview]
Message-ID: <20110927093743.GF3952@dell> (raw)
In-Reply-To: <1314180743-10067-1-git-send-email-lkslawek@gmail.com>
Hi Slawek,
(This starts off my round of "applied to github" notifications for
obexd)
On Wed, Aug 24, 2011, Slawomir Bochenski wrote:
> This replaces parsing missed calls listing that was used to get the
> number of missed calls that have been unread with a simple SPARQL
> query.
>
> Previous code was trying to deal with misbehaviour of commhistoryd but
> still was failing in some cases. commhistoryd is now fixed.
> ---
> plugins/phonebook-tracker.c | 105 +++++++++----------------------------------
> 1 files changed, 22 insertions(+), 83 deletions(-)
Applied. Thanks.
Johan
prev parent reply other threads:[~2011-09-27 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 10:12 [PATCH obexd] Simplify counting new missed calls Slawomir Bochenski
2011-09-27 9:37 ` Johan Hedberg [this message]
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=20110927093743.GF3952@dell \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lkslawek@gmail.com \
/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).