> Andrew> It's not done by my MUA, and it's present in your latest posted
> Andrew> patch. If anything I'd suspect your MUA:
>
> The patch in the original email is in text/plain with base64 transfer
> encoding, which means that CRLF line endings are mandatory. It's
> actually up to the receiving MUA (or the archives webserver) to undo
> that.
I came to the same conclusion. This is hidden because most people post
patches as "application/octet-stream", where no meddling is allowed. I'll
try to do that in the future.
> If the archives webserver isn't handling that then it's a bug there.
I'm not sure that the webserver is at fault either: it sends "CRLF" on
"text/plain", which seems okay, even required, by MIME. Maybe the web
user agent should do the translating if appropriate to the receiving
system... Obviously "curl" does not do it, nor "firefox" on "save as".
I have no doubt that some MUA around would forget to do the conversion.
--
Fabien.