Attachment 87067 Details for Bug 54879 – [next 11/22] Adjust contact features to Telepathy-1 API: quarks, not an enum

[patch] [next 11/22] Adjust contact features to Telepathy-1 API: quarks, not an enum

0011-Adjust-contact-features-to-Telepathy-1-API-quarks-no.patch (text/plain), 1.16 KB, created by Simon McVittie on 2013-10-03 17:21:11 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2013-10-03 17:21:11 UTC

Size: 1.16 KB

patch

obsolete

>From f0d02e21e8cd66c5e2a6e0ff7d282d83f229218f Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Thu, 26 Sep 2013 20:15:16 +0100
>Subject: [PATCH 11/22] Adjust contact features to Telepathy-1 API: quarks, not
> an enum
>
>---
> src/mcd-account.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
>diff --git a/src/mcd-account.c b/src/mcd-account.c
>index 736669e..cdc20e8 100644
>--- a/src/mcd-account.c
>+++ b/src/mcd-account.c
>@@ -5038,7 +5038,8 @@ mcd_account_self_contact_changed_cb (McdAccount *self,
>       TP_CONTACT_FEATURE_AVATAR_TOKEN,
>       TP_CONTACT_FEATURE_AVATAR_DATA,
>       TP_CONTACT_FEATURE_ALIAS,
>-      TP_CONTACT_FEATURE_PRESENCE
>+      TP_CONTACT_FEATURE_PRESENCE,
>+      0
>   };
>   TpContact *self_contact;
> 
>@@ -5060,8 +5061,7 @@ mcd_account_self_contact_changed_cb (McdAccount *self,
>       tp_contact_get_identifier (self_contact));
> 
>   tp_connection_upgrade_contacts_async (tp_connection,
>-      1, &self_contact,
>-      G_N_ELEMENTS (contact_features), contact_features,
>+      1, &self_contact, contact_features,
>       mcd_account_self_contact_upgraded_cb,
>       tp_weak_ref_new (self, NULL, NULL));
> }
>-- 
>1.8.4.rc3
>

Actions: View | Splinter Review

Attachments on bug 54879: 87050 | 87051 | 87052 | 87053 | 87054 | 87055 | 87057 | 87058 | 87059 | 87060 | 87061 | 87062 | 87063 | 87064 | 87065 | 87066 | 87067 | 87068 | 87069 | 87070 | 87071 | 87072 | 87073 | 87074 | 87075 | 87076 | 87077 | 87078

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.