Re: [PATCH 0/3] SHA-256: Update commit-graph and multi-pack-index formats
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 14, 2020, 19:25 UTC
- Message-ID
- <xmqqeeo9vxl0.fsf@gitster.c.googlers.com>
- In-Reply-To
- <pull.703.git.1597428440.gitgitgadget@gmail.com>
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 9 quoted lines
> As discussed [1], there is some concern around binary file formats requiring > the context of the repository config in order to infer hash lengths. Two > formats that were designed with the hash transition in mind (commit-graph > and multi-pack-index) have bytes available to indicate the hash algorithm > used. Let's actually update these formats to be more self-contained with the > two hash algorithms being available. > ... > If this is the way we want to go with the formats, then I'll assist > coordinating these textual and semantic merge conflicts.
I agree that the files should be self-identifying, but have these changes tested without sha256 hash?