On Fri, Jul 01 2022, Yuri D'Elia wrote: > Just trying out the current main branch to play with the current version > of the --ext-exit option :). Thanks for considering this, it's quite > convenient to trigger local hooks.
I would still consider, if possible, to include a way to distinguish between temporary errors (all network errors) and hard errors. My original patch was also not great for this. The reasoning is that it's currently impossible to know if mbsync exited due to a network timeout (which is quite common - and I want to ignore if happening randomly in my logs), or whether the configuration file has syntax errors, the local journal is corrupted, etc. In the first case, retrying is a possibility. In the second retrying will get you nowhere. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
