docs: fix step in transition plan
One of the required steps for the objectFormat extension is to implement the loose object index. However, without support for compatObjectFormat, we don't even know if the loose object index is needed, so it makes sense to move that step to the compatObjectFormat section. Do so. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
brian m. carlson committed
Aug 13, 2020 at 22:49 UTC
2ae12e568b14e068cd37afdd47dd46c2be8538fe
1 file changed
+1
-1
Documentation/technical/hash-function-transition.txt
+1
-1
@@ -650,7 +650,6 @@ Some initial steps can be implemented independently of one another:
650
651
The first user-visible change is the introduction of the objectFormat
652
extension (without compatObjectFormat). This requires:
653
-- implementing the loose-object-idx
653
- teaching fsck about this mode of operation
654
- using the hash function API (vtable) when computing object names
655
- signing objects and verifying signatures
@@ -658,6 +657,7 @@ extension (without compatObjectFormat). This requires:
657
repository
658
659
Next comes introduction of compatObjectFormat:
660
+- implementing the loose-object-idx
661
- translating object names between object formats
662
- translating object content between object formats
663
- generating and verifying signatures in the compat format