Re: What's cooking in git.git (May 2019, #02; Tue, 14)

From: Elijah Newren <newren@gmail.com>
Date: May 13, 2019, 22:20 UTC
Message-ID: <CABPp-BGPrDfHjQoASFFbyt2v3Aa6vie5H5U2KOWUnu=_NEiPyA@mail.gmail.com>
In-Reply-To: <xmqqa7fqbahj.fsf@gitster-ct.c.googlers.com>

On Mon, May 13, 2019 at 12:27 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 12 quoted lines

> * en/fast-export-encoding (2019-05-13) 5 commits
>  - fast-export: do automatic reencoding of commit messages only if requested
>  - fast-export: differentiate between explicitly utf-8 and implicitly utf-8
>  - fast-export: avoid stripping encoding header if we cannot reencode
>  - fast-import: support 'encoding' commit header
>  - t9350: fix encoding test to actually test reencoding
>
>  The "git fast-export/import" pair has been taught to handle commits
>  with log messages in encoding other than UTF-8 better.
>
>  Will merge to 'next'.
>  cf. <20190510205335.19968-1-newren@gmail.com>

I sent out a v4 this morning with Torsten's suggested YES|NO wording, your suggestion of more aliases for "yes"/"no", and based on Dscho's clarification I was able to update the tests to be more precise. I again tested with Dscho's gitgitgadget Azure pipelines integration to verify it works on the major platforms. Could you merge it (cf. <20190513164722.31534-1-newren@gmail.com>) instead of the v3 you currently have in en/fast-export-encoding?

Elijah