On 11/6/23 7:16 AM, Daniel P. Berrangé wrote:
On Mon, Nov 06, 2023 at 12:45:22PM +0100, Michal Prívozník wrote:
On 11/6/23 11:54, Andrea Bolognani wrote:
On Mon, Nov 06, 2023 at 10:26:36AM +0000, Daniel P. Berrangé wrote:
On Mon, Nov 06, 2023 at 02:21:16AM -0800, Andrea Bolognani wrote:
So does that mean that the issue is server-side? I'm pretty sure
Laine, Martin and I are all fetching emails using different tools, so
that would sound more plausible, but it's weird that things
apparently work fine for you?
I guess I tested the wrong mail. I can apply patches from Laine, but
I cannot apply from Michal.
I think the trigger is non-ASCII7 characters (ie accents) in the sender
name (or possibly the Signed-off-by), causing software to re-encode turn
the message into base64
Until this is sorted out, passing
--quoted-cr=strip
to 'git am' seems to do the trick.
Alternatively, might as well start sending base64 encoded patches, list
re-encodes them anyway:
git send-email --transfer-encoding=base64 ...
Please don't. base64 encoding is horrible if someone needs to just
view mbox contents directly.
Maybe Michal just forgot the </s> at the end of his comment? Yeah, there
have been occasions when I was doing some random thing and clicked on a
link that led to a page that was just base64, and it really is not a
pleasing experience.
Seriously, if accented characters in mail wasn't triggering this before,
then hopefully it's possible to make it work correctly now with the
"newer better stronger faster mailman" (Copyright (c) Daft Punk)
<whatyearisthis.gif>
_______________________________________________
Devel mailing list -- devel@xxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxx
