From: Ben Hutchings <[email protected]> Date: Wed, 20 Feb 2013 04:07:49 +0000
> It seems to be converting, not auto-detecting. And it doesn't do > anything about the headers inside the mbox. So if I don't fix these up > then git will warn, for example: > > Applying: tcp: fix for zero packets_in_flight was too broad > Warning: commit message does not conform to UTF-8. > You may want to amend it after fixing the message, or set the config > variable i18n.commitencoding to the encoding your project uses. > > and the commit message has accented characters corrupted. Ok, thanks for the info, I'm surprised Greg never saw this. Maybe we've just been lucky in the past and not too many umulauts in the commit author's names :-) >> I bet you just save the attachment and no changes happen to the >> content whatsoever. > > Indeed: the text is not (AFAIK) converted at my end, so I get an mbox > file where each message says it's in UTF-8 but it's actually in ISO > 8859-1. I'll look into fixing this, thanks a lot Ben. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
