On 01/03/16 02:09, J William Piggott wrote:
On 02/23/2016 09:17 PM, Paul Eggert wrote:
In reviewing this patch I had problems with the way it was encoded.
So, I forced my MUA to send the latest patch set with iso_8859-1 encoding, for which it sets this header:
Content-Type: text/plain; charset=windows-1252
But I see that [PATCH 04/10] was change to:
Content-Type: text/plain; charset=UTF-8
It was sent the same way as the rest of the set, I do not know where in the chain it was clobbered.
Some of those patches look a little odd when viewed in an MUA anyway (Thunderbird or Icedove in my case), as the MIME charset is declared as windows-1252, but the actual text is UTF-8. (That's most prevalent in the changes to zone1970.tab by PATCH 10/10.) At least your MUA doesn't seem to screw up inline patches completely like most do! I generally use git send-email to send inline patches. -- -=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=- -=( Web: http://www.mev.co.uk/ )=-