On Fri, May 22, 2026 at 01:43:26PM +1000, Seth McDonald wrote:
I wouldn't mention drivers since that's an implementation detail the
user wouldn't know about.
good point, the concept is mentioned only briefly in the debug section.
That said, since the UID data shouldn't change between a dry and real
run, is there any technical reason why we can't have the dry run
operate read-only on the uid database/validity file?
as i said, the imap server will do it anyway, and there is nothing isync
could do about it. it seems acceptable, and arguably even desirable to
keep the behavior consistent between backends.
also, i still don't see a _good_ use case for true read-only operation.
so we would be adding implementation complexity for a useless and
arguably even counter-productive feature. that makes no sense.
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
