---- Reported by email@example.com 2011-10-26 12:15:48 +0000 ----
This can be automated by running a sync and making changes via a second client, similar to the interrupted sync tests.
Need a complete list of scenarios and the expected outcome:
* new item on peer gets removed => remove it sooner or later (next session?)
* new item on peer gets updated => transfer new data immediately or in next session
* same item gets added by first and second client => only add once, merge if necessary
* existing item gets updated by first and second client => merge and keep most recent data
--- Bug imported by firstname.lastname@example.org 2012-07-29 20:36 UTC ---
This bug was previously known as _bug_ 23770 at https://bugs.meego.com/show_bug.cgi?id=23770
-- 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/107.