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

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 10, 2019, 18:51 UTC
Message-ID: <nycvar.QRO.7.76.6.1907102050100.46@tvgsbejvaqbjf.bet>
In-Reply-To: <xmqq36jeva9e.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Tue, 9 Jul 2019, Junio C Hamano wrote:

Show 16 quoted lines

> * mt/dir-iterator-updates (2019-06-25) 10 commits
>  - clone: replace strcmp by fspathcmp
>  - clone: use dir-iterator to avoid explicit dir traversal
>  - clone: extract function from copy_or_link_directory
>  - clone: copy hidden paths at local clone
>  - dir-iterator: add flags parameter to dir_iterator_begin
>  - dir-iterator: refactor state machine model
>  - dir-iterator: use warning_errno when possible
>  - dir-iterator: add tests for dir-iterator API
>  - clone: better handle symlinked files at .git/objects/
>  - clone: test for our behavior on odd objects/* content
>
>  Adjust the dir-iterator API and apply it to the local clone
>  optimization codepath.
>
>  Is this ready for 'next'?

I am afraid that still, just like I said in response to the previous "What's cooking" mail, this is not ready (which is unsurprising, given that it has not changed): it breaks 1,384 test cases. For details, see https://dev.azure.com/gitgitgadget/git/_build/results?buildId=11495&view=ms.vss-test-web.build-test-results-tab

Ciao, Dscho