https://bugs.kde.org/show_bug.cgi?id=386985
--- Comment #28 from Huw <hu...@mailbox.org> --- I'm no dev so apologies if I've got this wrong, but from my reading of the submission on Phabricator, couldn't this be resolved if CalDav used *both* methods to sync with the server? Surely some code could be inserted to handle a null result, while then using output from the other result? Is it really the case that the patch was rejected just because it breaks sync for Kolab users, despite the current situation breaking sync for apparently a whole host of other servers? -- You are receiving this mail because: You are the assignee for the bug.
