Documentation/gitformat-pack.txt: remove multi-cruft packs alternative
This text, originally from 3d89a8c118 (Documentation/technical: add cruft-packs.txt, 2022-05-20) lists multiple cruft packs as a potential alternative to the design of cruft packs. We have always supported multiple cruft packs (i.e. we use the most recent mtime for a given object among all cruft packs which contain it, etc.), but haven't encouraged its use. We still aren't encouraging users to go out and generate multiple cruft packs, but let's take a step in that direction by dropping language that suggests we aren't capable of working with multiple cruft packs. Signed-off-by: Taylor Blau <me@ttaylorr.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Taylor Blau committed
Aug 28, 2023 at 18:49 UTC
3843ef89312593a1e4d70bcdb29fd6ffa87134d6
1 file changed
+1
-9
Documentation/gitformat-pack.txt
+1
-9
@@ -618,21 +618,13 @@ understand cruft packs.
618
619
Notable alternatives to this design include:
620
621
- - The location of the per-object mtime data, and
622
- - Storing unreachable objects in multiple cruft packs.
621
+ - The location of the per-object mtime data.
622
623
On the location of mtime data, a new auxiliary file tied to the pack was chosen
624
to avoid complicating the `.idx` format. If the `.idx` format were ever to gain
625
support for optional chunks of data, it may make sense to consolidate the
626
`.mtimes` format into the `.idx` itself.
627
629
-Storing unreachable objects among multiple cruft packs (e.g., creating a new
630
-cruft pack during each repacking operation including only unreachable objects
631
-which aren't already stored in an earlier cruft pack) is significantly more
632
-complicated to construct, and so aren't pursued here. The obvious drawback to
633
-the current implementation is that the entire cruft pack must be re-written from
634
-scratch.
635
-
628
GIT
629
---
630
Part of the linkgit:git[1] suite