unpack-trees: take care to propagate the split-index flag
commit061dd722dcc7a0e1f506c426ff6591b0ca8f14b6
authorJohannes Schindelin <johannes.schindelin@gmx.de>
Sun, 26 Mar 2023 22:45:43 +0000 (26 22:45 +0000)
committerJunio C Hamano <gitster@pobox.com>
Mon, 27 Mar 2023 16:40:40 +0000 (27 09:40 -0700)
treebecf0f0d93c181d9406440813bf3e3d4268a726a
parentbe6b65b91bb48c9399c8a6a358dd29b198f2bd79
unpack-trees: take care to propagate the split-index flag

When copying the `split_index` structure from one index structure to
another, we need to propagate the `SPLIT_INDEX_ORDERED` flag, too, if it
is set, otherwise Git might forget to write the shared index when that
is actually needed.

It just so _happens_ that in many instances when `unpack_trees()` is
called, the result causes the shared index to be written anyway, but
there are edge cases when that is not so.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
unpack-trees.c