On Tue, 10 May 2005 11:39:45 PDT, "Perez-Gonzalez, Inaky" said: > >From: Oleg Nesterov > >"Perez-Gonzalez, Inaky" wrote: > Errr....shut, that was my or your email program screwing > things up...that =20, I mean, that's MIME for line break. Dug a bit further... There was a trailing blank in Inaky's note as it arrived here, but it was traveling with a Content-Type-Encoding: 8bit. My guess is that some mail software between vger and Oleg's inbox down-converted to 7bit. Either that mailer failed to insert a 'Content-Type-Encoding: quoted-printable' header when it applied the quoted-printable )changing a trailing blank to =20) when down-converting, or Oleg's mail reader (apparently Mozilla?) failed to heed the C-T-E and convert the =20 back to the trailing blank it should have been. I was there when all this MIME stuff was designed, and we covered all the failure modes of stupid designers of mail software that we could think of. We never considered the sorts of whitespace screw-ups we actually see today - I think there was a "No designer could be THAT daft" blind-spot....
Attachment:
pgptavZd9Kuc3.pgp
Description: PGP signature
- Prev by Date: Re: /proc/cpuinfo format - arch dependent!
- Next by Date: Re: /proc/cpuinfo format - arch dependent!
- Previous by thread: RE: [PATCH 2/4] rt_mutex: add new plist implementation
- Next by thread: RE: [PATCH 2/4] rt_mutex: add new plist implementation
- Index(es):
 |