---- Reported by jingke.zhang@intel.com 2010-04-13 02:15:27 +0000 ---- This is from http://bugzilla.moblin.org/show_bug.cgi?id=6365 Description From jku 2009-09-23 01:44:17 PST (-) [reply] Patrick wrote: > That reminds me: there are also several configuration changes which > should trigger a slow sync. We don't have any mechanism in place to > force this right now. The check would have to compare the config of the > last sync with the current config to determine whether "relevant" > properties have changed and .other.ini is still intact. "relevant" is a > bit hard to define, though. ------- Comment #2 From pohly 2009-10-02 00:26:39 PST (-) [reply] ------- Adding a <alertscript>FORCESLOWSYNC()</alertscript> to affected datastores should do the trick for the server. In a client, we can modify the sync mode that we send to the server. --- Bug imported by patrick.ohly@gmx.de 2012-07-29 20:36 UTC --- This bug was previously known as _bug_ 693 at https://bugs.meego.com/show_bug.cgi?id=693
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/117.
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.