On Sat, 2010-04-17 at 13:52 +0200, Patrick Ohly wrote: > We've had the same problem with Funambol. At that time I didn't have an > idea, but after writing down the explanation above and thinking some > more about it, here's something that might work: when a new VEVENT gets > added in Evolution with RECURRENCE-ID for an existing, unmodified > recurring event, then modify the recurring event by adding an exception. > Then sync both the main event and the child to the server.
Created an issue to track this: http://bugzilla.meego.com/show_bug.cgi?id=1180 -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
