Hi, Tino You're right! Thanks for your reminder. Patrick, it seems two patches are not merged into the master. I re-push them to the branch 'mb10458'. Could you please merge them?
Cheers, Yongsheng > -----Original Message----- > From: Tino Keitel [mailto:[email protected]] > Sent: Tuesday, April 13, 2010 5:24 AM > To: Ohly, Patrick; Zhu, Yongsheng; [email protected] > Subject: Re: [SyncEvolution] syncevolution --daemon=yes/no (was: RE: Alarms in > the calendar: Evolution vs. vcal) > > On Mon, Apr 12, 2010 at 23:16:53 +0200, Tino Keitel wrote: > > [...] > > > I tested the master branch as of today. Alarms are transfered from the > > mobile into Evolution, but not in the other direction. Alarms created > > in Evolution have no alarm set on the mobile. It works when going back > > to the version from the mb10458 branch. > > > > Could you give me a hint what commits are related to this issue? I only > > found 15c581f83025dc0250b978f431ede85ae2f9a545, which fixes the mobile > > -> Evolution direkction. I can not find the fix for the other > > direction. > > In the old mb10458 branch (before it was rebased), there was a commit > e554b749bf4378e829f9b9b12c667cae09a04acc: > > Calendar: add workaround for 'alarm' in vCalendar1.0 (MB#10458) > > Mobical.net syncML server only accepts 'trigger' time > of alarms as 'UTC' time. If 'trigger' time is a duration, > it ignores that. > > To prevent this, when the outgoing format is 'vCalendar1.0', > convert the duration time into 'UTC' time. > > This is missing in the current mb10458 and master branches. I guess > that this is the reason for lost alarms on the phone when creating an > appointment in Evolution. > > Regards, > Tino _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
