Perform conflict resolution in sequence
This is expected to launch an interactive tool; there's no point in
doing them in sequence.
Remove no-op collections from the plan
I only needed to include no-op plans in order to extract the
mapping_uid, which was then used to filter stale collections.
After filtering stale collections, filter out the no-op plans.
Clear stale mappings from the status database
When a collection no longer exists, remove it entirely from the status
database. If another collection with the same href is created in future,
it will not use any leftover data.
Implements: https://todo.sr.ht/~whynothugo/vdirsyncer-rs/105
vdirsyncer: improve error output
Remove obsolete FIXME
We're not doing item properties.
Improve handling of skipped/protected collections
Only skip plan if a single side is empty
If both have been emptied we should proceed. This will typically update
the status DB.
Use an Arc for CollectionId
readme: also link to davcli
readme: rename Credits -> Thanks
Use h2 for subsection titles
readme: improve dev documentation
And link to related libraries.
Rename confusing function
readme: requirements, compilation, installation...
make; skip linking when checking
config: reject bogus collection directive
When one than more parameter is passed, bail. At most one parameter is
allowed.
Simplify boolean expressions
Use `Option<&T>` instead of `&Option<T>`