mirror of
https://github.com/inverse-inc/sogo.git
synced 2026-11-20 14:36:53 +00:00
When one save changes several occurrences, each change is sent to the attendees in turn. If a later change was refused, for example because a resource was already booked, the earlier changes had already reached the attendees while the organizer's calendar was left unchanged. Run the booking and availability checks for all changes first, and send nothing if one of them fails. A save with a single change skips this step, because the normal check already covers it.