--- Comment #7 from pohly <patrick.ohly(a)intel.com> 2009-07-25 09:40:24 ---
(In reply to comment #6)
(In reply to comment #5)
> (In reply to comment #3)
> > a typo: no "slow-way", should be "slow" :)
> > (In reply to comment #2)
> > > What I have learned from these steps is that 'two-way' doesn't
> > > normally after slow-way synchronization.
> > >
> I can reproduce this 100% of the time with SyncEvolution 0.9.
> I can not reproduce this ever with SyncEvolution 0.8.1a.
> In my brief look at why I suspect a mapping problem after the slow sync in
SyncEvolution doesn't do any mapping. How can it have a problem with it then?
Let me explain in more detail: SyncEvolution never keeps a mapping *after* a
sync. *During* this particular slow sync it also shouldn't have to send a
mapping, because it sends the LUID, the server matches the item and remembers
The only time when the client has to send a mapping is when the server adds a
new item to the client, which shouldn't be the case here.
Or did you see something else happening when you tested it?
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.