On Mon, May 13, 2019 at 04:17:24PM -0700, Elijah Newren wrote:
> When fast-export encounters a commit with an 'encoding' header, it tries
> to reencode in utf-8 and then drops the encoding header. However, if it
> fails to reencode in utf-8 because e.g. one of the characters in the
> commit messag
When fast-export encounters a commit with an 'encoding' header, it tries
to reencode in utf-8 and then drops the encoding header. However, if it
fails to reencode in utf-8 because e.g. one of the characters in the
commit message was invalid in the old encoding, then we need to retain
the original
2 matches
Mail list logo