[PATCH 07/15] Encode utf-8 argument for md5 function
dolohow at outlook.com
Mon May 16 22:43:53 BST 2016
> > > * Forget about the names and let's break the setups.
> > I guess we will have complaints. Also, I'm not sure what we do when MD5
> > does not match. I worry about email deletions on remote if the filenames
> > are fully ignored by the merge algo.
> I've changed my mind about that. I've always made it clear such tricks
> is not supported. Same goes for the decodefoldernames configuration
> With this in mind, it's not fair that I force you to do the job of
> supporting this use case. Supporting UTF-8 correctly can be implemented
> later if someone having this setup cares enough.
> If it's ok for you, I'll tune the commit message to add explanations
> that we know this breaks UTF-8 and why this was merged anyway.
Sure, but I guess "[PATCH 11/15] Do not encode elements of list" should
goes in the same commit as this one. I can create a seperate patch that
will cover that.
What do you think?
More information about the OfflineIMAP-project