freshlybakedca.ke / git
Git fork
fork atom

Documentation: remove a "future work" item from the MIDX docs

One of the items listed as "future work" in the MIDX's technical
documentation is to extend the format to allow MIDXs to be written
incrementally across multiple layers.

This was suggested all the way back in ceab693d1f (multi-pack-index: add
design document, 2018-07-12), and implemented in b9497848df (Merge
branch 'tb/incremental-midx-part-1', 2024-08-19). Let's remove it
accordingly.

Signed-off-by: Taylor Blau <me@ttaylorr.com>
Acked-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

authored by

Taylor Blau and committed by
Junio C Hamano 4a9179d1 683c54c9

-10
-10
Documentation/technical/multi-pack-index.adoc
··· 167 167 Future Work 168 168 ----------- 169 169 170 - - The multi-pack-index allows many packfiles, especially in a context 171 - where repacking is expensive (such as a very large repo), or 172 - unexpected maintenance time is unacceptable (such as a high-demand 173 - build machine). However, the multi-pack-index needs to be rewritten 174 - in full every time. We can extend the format to be incremental, so 175 - writes are fast. By storing a small "tip" multi-pack-index that 176 - points to large "base" MIDX files, we can keep writes fast while 177 - still reducing the number of binary searches required for object 178 - lookups. 179 - 180 170 - If the multi-pack-index is extended to store a "stable object order" 181 171 (a function Order(hash) = integer that is constant for a given hash, 182 172 even as the multi-pack-index is updated) then MIDX bitmaps could be