Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> writes: > On Mon, Aug 06 2018, Junio C Hamano wrote: > >> * ab/newhash-is-sha256 (2018-08-06) 2 commits >> - doc hash-function-transition: pick SHA-256 as NewHash >> - doc hash-function-transition: note the lack of a changelog >> >> Documentation update. >> >> Will Merge to 'next'. > > The tip of gitster/ab/newhash-is-sha256 has a unicode-corrupted > signed-off-by line from me. See > https://github.com/git/git/commit/f855a19d45 not sure how that got > there... Hmph, it came from this message (most headers omitted) To: =?iso-8859-1?Q?=C6var_Arnfj=F6r=F0?= Bjarmason <avarab@xxxxxxxxx> Message-ID: <20180804085247.GE55869@xxxxxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit Subject: doc hash-function-transition: pick SHA-256 as NewHash ... Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> and the body seems to be correct iso-8859-1. "od -cx" tells me that the file stores 0xf0 for that D looking thing, for example. Could it be mailinfo that screws up, I wonder. A quick check with "git mailinfo" does not give me anything suspicous---the info contents emitted to its standard output is correctly converted to UTF-8. Puzzled... I read from public-inbox/git over nntp, if that matters.
