[evolution-mapi] Collection backend schedules two 'populate' requests after going online



commit 6681d6072f3bcb7d01836a6f7da17c47277ee58f
Author: Milan Crha <mcrha redhat com>
Date:   Thu Sep 27 10:55:06 2018 +0200

    Collection backend schedules two 'populate' requests after going online
    
    ECollectionBackend base class makes sure the 'populate' method is called
    after the backend itself goes online, thus there is no need to schedule
    it in the descendant again.
    
    Related to https://gitlab.gnome.org/GNOME/evolution-data-server/issues/36

 src/collection/e-mapi-backend.c | 4 ----
 1 file changed, 4 deletions(-)
---
diff --git a/src/collection/e-mapi-backend.c b/src/collection/e-mapi-backend.c
index 937ab08..f9c64f4 100644
--- a/src/collection/e-mapi-backend.c
+++ b/src/collection/e-mapi-backend.c
@@ -986,10 +986,6 @@ e_mapi_backend_init (EMapiBackend *backend)
                g_free,
                g_object_unref);
 
-       g_signal_connect (
-               backend, "notify::online",
-               G_CALLBACK (mapi_backend_populate), NULL);
-
        g_mutex_init (&backend->priv->credentials_lock);
        backend->priv->credentials = NULL;
 }


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]