summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@gmx.de>2008-07-12 19:31:03 +0000
committerPatrick Ohly <patrick.ohly@gmx.de>2008-07-12 19:31:03 +0000
commitb77808a909bbba36f71aaccb30857e62a723dd43 (patch)
treea9a9050bf7de1f9763b40e5390e6339ec63b0798 /NEWS
parent3660154d90542df640237d52269b954492c8c788 (diff)
Mac OS X client now uses the new TrackingSyncSource
git-svn-id: https://zeitsenke.de/svn/SyncEvolution/trunk@670 15ad00c4-1369-45f4-8270-35d70d36bdcd
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS12
1 files changed, 11 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index 236f0eb6..25aa9bd7 100644
--- a/NEWS
+++ b/NEWS
@@ -60,6 +60,16 @@ C++ client library: the frozen 7.0 code, but before the release
affects the enabled ones, as intended. To enable disabled sync sources,
list them after the server name.
+*** WARNING ***: this version uses a different change tracking for
+for Mac OS X AddressBook. After switching from a previous release to the current
+one or vice versa, do a "syncevolution --sync --refresh-from-server"
+once to reset the change tracking. Not doing so can result in applying
+the same changes to the server multiple times and thus duplicates.
+
+A similar change was necessary in 0.8 alpha 1 for Evolution calendar,
+tasks, and memos. When switching from a version >= 0.8 alpha 1 to an
+older version or vice versa also refresh the local databases.
+
SyncEvolution 0.7 -> 0.8 alpha 1, 19.04.2008
--------------------------------------------
@@ -70,7 +80,7 @@ configuration layout. Old configurations still work. They can be
converted to the new format via a new "--migrate" command line option.
*** WARNING ***: this version uses a different change tracking for
-calendars, task lists and memos. After switching from a previous
+Evolution calendars, task lists and memos. After switching from a previous
release to the current one or vice versa, do a "syncevolution --sync
--refresh-from-server" once to reset the change tracking. Not doing so
can result in applying the same changes to the server multiple times