nd/index-dump-in-json, was Re: What's cooking in git.git (Jul 2019, #01; Wed, 3)

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 4, 2019, 09:32 UTC
Message-ID: <nycvar.QRO.7.76.6.1907041131270.44@tvgsbejvaqbjf.bet>
In-Reply-To: <xmqqpnmqzrbg.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Wed, 3 Jul 2019, Junio C Hamano wrote:

Show 18 quoted lines

> * nd/index-dump-in-json (2019-06-26) 11 commits
>  - SQUASH???
>  - t3008: use the new SINGLE_CPU prereq
>  - read-cache.c: dump "IEOT" extension as json
>  - read-cache.c: dump "EOIE" extension as json
>  - resolve-undo.c: dump "REUC" extension as json
>  - fsmonitor.c: dump "FSMN" extension as json
>  - split-index.c: dump "link" extension as json
>  - dir.c: dump "UNTR" extension as json
>  - cache-tree.c: dump "TREE" extension as json
>  - read-cache.c: dump common extension info in json
>  - ls-files: add --json to dump the index
>
>  "ls-files" learned "--debug-json" option to dump the contents and
>  the extensions of the index file.
>
>  At least the fixup at the tip needs to be squashed into the right
>  commit.

... and the test flakiness should be analyzed. It might be an indicator of a bug: why else would an index extension sometimes be omitted? It could even be a bug in the code that updates the index, where it might "forget" the extension from time to time.

Ciao, Dscho