diff options
author | Ben Peart <benpeart@microsoft.com> | 2018-10-10 11:59:34 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2018-10-11 15:32:48 +0900 |
commit | 3b1d9e045e1ad6c2cd5cbe668ccb740a82b50efb (patch) | |
tree | 1c4d899ab517c0cc66684dbac838eaf13eed4bc6 /apply.c | |
parent | read-cache: clean up casting and byte decoding (diff) | |
download | tgif-3b1d9e045e1ad6c2cd5cbe668ccb740a82b50efb.tar.xz |
eoie: add End of Index Entry (EOIE) extension
The End of Index Entry (EOIE) is used to locate the end of the variable
length index entries and the beginning of the extensions. Code can take
advantage of this to quickly locate the index extensions without having
to parse through all of the index entries.
The EOIE extension is always written out to the index file including to
the shared index when using the split index feature. Because it is always
written out, the SHA checksums in t/t1700-split-index.sh were updated
to reflect its inclusion.
It is written as an optional extension to ensure compatibility with other
git implementations that do not yet support it. It is always written out
to ensure it is available as often as possible to speed up index operations.
Because it must be able to be loaded before the variable length cache
entries and other index extensions, this extension must be written last.
The signature for this extension is { 'E', 'O', 'I', 'E' }.
The extension consists of:
- 32-bit offset to the end of the index entries
- 160-bit SHA-1 over the extension types and their sizes (but not
their contents). E.g. if we have "TREE" extension that is N-bytes
long, "REUC" extension that is M-bytes long, followed by "EOIE",
then the hash would be:
SHA-1("TREE" + <binary representation of N> +
"REUC" + <binary representation of M>)
Signed-off-by: Ben Peart <benpeart@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'apply.c')
0 files changed, 0 insertions, 0 deletions