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

> On 30 Mar 2018, at 12:32, Lars Schneider wrote: > > >> On 30 Mar 2018, at 11:24, Ævar Arnfjörð Bjarmason wrote: >> >> >> On Wed, Mar 28 2018, Junio C. Hamano wrote: >> >>> * ls/checkout-encoding (2018-03-16) 10 commits >>> - convert: add round

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

> On 30 Mar 2018, at 11:24, Ævar Arnfjörð Bjarmason wrote: > > > On Wed, Mar 28 2018, Junio C. Hamano wrote: > >> * ls/checkout-encoding (2018-03-16) 10 commits >> - convert: add round trip check based on 'core.checkRoundtripEncoding' >> - convert: add tracing for

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

On Wed, Mar 28 2018, Junio C. Hamano wrote: > * 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 > -

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

>> * sb/packfiles-in-repository (2018-03-26) 12 commits > ... >> >> (this branch uses nd/remove-ignore-env-field and sb/object-store.) >> >> Refactoring of the internal global data structure continues. >> >> Waiting for a follow-up discussion. > > I'll review this one more closely and start a

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

On Wed, Mar 28, 2018 at 12:58 PM, Junio C Hamano wrote: > > * ab/doc-hash-brokenness (2018-03-27) 2 commits > - doc hash-function-transition: clarify what SHAttered means > - doc hash-function-transition: clarify how older gits die on NewHash This looked ready for next to

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

On 03/28, Junio C Hamano wrote: > * bw/protocol-v2 (2018-03-15) 35 commits > - remote-curl: don't request v2 when pushing > - remote-curl: implement stateless-connect command > - http: eliminate "# service" line when using protocol v2 > - http: don't always add Git-Protocol header > - http:

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

Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. Git 2.17 final is expected to be