Re: What's cooking in git.git (Mar 2018, #05; Wed, 28)

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Mar 30, 2018, 09:24 UTC
Message-ID: <87lge9x6e3.fsf@evledraar.gmail.com>
In-Reply-To: <xmqqsh8k6khj.fsf@gitster-ct.c.googlers.com>

On Wed, Mar 28 2018, Junio C. Hamano wrote:

Show 15 quoted lines

> * ls/checkout-encoding (2018-03-16) 10 commits
>  - convert: add round trip check based on 'core.checkRoundtripEncoding'
>  - convert: add tracing for 'working-tree-encoding' attribute
>  - convert: check for detectable errors in UTF encodings
>  - convert: add 'working-tree-encoding' attribute
>  - utf8: add function to detect a missing UTF-16/32 BOM
>  - utf8: add function to detect prohibited UTF-16/32 BOM
>  - utf8: teach same_encoding() alternative UTF encoding names
>  - strbuf: add a case insensitive starts_with()
>  - strbuf: add xstrdup_toupper()
>  - strbuf: remove unnecessary NUL assignment in xstrdup_tolower()
>
>  The new "checkout-encoding" attribute can ask Git to convert the
>  contents to the specified encoding when checking out to the working
>  tree (and the other way around when checking in).

There's an issue in ca16fc3635 ("convert: check for detectable errors in UTF encodings", 2018-03-15) flagged by Coverity: https://public-inbox.org/git/CAGZ79kbAOcwaRzjuMtZ_HVsYvUr_7UAPbOcnrmPgsdE19q=PrQ@mail.gmail.com/