From: Johan Hedberg <johan.hedberg@nokia.com>
To: Radoslaw Jablonski <ext-jablonski.radoslaw@nokia.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/3] Refactoring of vcard content structures
Date: Fri, 14 Jan 2011 11:05:12 +0000 [thread overview]
Message-ID: <20110114110512.GA19145@jh-x301> (raw)
In-Reply-To: <1294904341-16047-1-git-send-email-ext-jablonski.radoslaw@nokia.com>
Hi Radek,
On Thu, Jan 13, 2011, Radoslaw Jablonski wrote:
> Structures for holding data about phone numbers, emails and
> addressess were practically identical and there was no sense
> to handle them differently. Now for saving informations about
> field content and type struct "phonebook_field" is used.
> ---
> plugins/phonebook-tracker.c | 59 ++++++++++++++++++------------------------
> plugins/vcard.c | 57 +++++++++++++++--------------------------
> plugins/vcard.h | 28 ++++----------------
> 3 files changed, 52 insertions(+), 92 deletions(-)
All three patches have been pushed upstream. Thanks.
Johan
prev parent reply other threads:[~2011-01-14 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 7:38 [PATCH 1/3] Refactoring of vcard content structures Radoslaw Jablonski
2011-01-14 11:05 ` 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=20110114110512.GA19145@jh-x301 \
--to=johan.hedberg@nokia.com \
--cc=ext-jablonski.radoslaw@nokia.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