2 .\" Title: gitformat-commit-graph
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/>
7 .\" Source: Git 2.47.0.rc0
10 .TH "GITFORMAT\-COMMIT\-GRAPH" "5" "2024-09-25" "Git 2\&.47\&.0\&.rc0" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 gitformat-commit-graph \- Git commit\-graph format
35 $GIT_DIR/objects/info/commit\-graph
36 $GIT_DIR/objects/info/commit\-graphs/*
40 The Git commit\-graph stores a list of commit OIDs and some associated metadata, including:
50 The generation number of the commit\&.
83 The parents of the commit, stored using positional references within the graph file\&.
94 The Bloom filter of the commit carrying the paths that were changed between the commit and its first parent, if requested\&.
97 These positional references are stored as unsigned 32\-bit integers corresponding to the array position within the list of commit OIDs\&. Due to some special constants we use to track parents, we can store at most (1 << 30) + (1 << 29) + (1 << 28) \- 1 (around 1\&.8 billion) commits\&.
98 .SH "COMMIT\-GRAPH FILES HAVE THE FOLLOWING FORMAT:"
100 In order to allow extensions that add extra data to the graph, we organize the body into "chunks" and provide a binary lookup table at the beginning of the body\&. The header includes certain values, such as number of chunks and hash type\&.
102 All multi\-byte numbers are in network byte order\&.
110 The signature is: {\*(AqC\*(Aq, \*(AqG\*(Aq, \*(AqP\*(Aq, \*(AqH\*(Aq}
120 1\-byte version number:
121 Currently, the only valid version is 1\&.
132 We infer the hash length (H) from this value:
135 If the hash type does not match the repository\*(Aqs hash algorithm, the
136 commit\-graph file should be ignored with a warning presented to the
147 1\-byte number (C) of "chunks"
157 1\-byte number (B) of base commit\-graphs
158 We infer the length (H*B) of the Base Graphs chunk
170 (C + 1) * 12 bytes listing the table of contents for the chunks:
171 First 4 bytes describe the chunk id\&. Value 0 is a terminating label\&.
172 Other 8 bytes provide the byte\-offset in current file for chunk to
173 start\&. (Chunks are ordered contiguously in the file, so you can infer
174 the length using the next chunk position if necessary\&.) Each chunk
175 ID appears at most once\&.
185 The CHUNK LOOKUP matches the table of contents from
186 the chunk\-based file format, see linkgit:gitformat\-chunk[5]
196 The remaining data in the body is described one chunk at a time, and
197 these chunks may be given in any order\&. Chunks are required unless
198 otherwise specified\&.
206 .nr an-no-space-flag 1
210 \fBOID Fanout (ID: {O, I, D, F}) (256 * 4 bytes)\fR
217 The ith entry, F[i], stores the number of OIDs with first
218 byte at most i\&. Thus F[255] stores the total
219 number of commits (N)\&.
227 .nr an-no-space-flag 1
231 \fBOID Lookup (ID: {O, I, D, L}) (N * H bytes)\fR
238 The OIDs for all commits in the graph, sorted in ascending order\&.
246 .nr an-no-space-flag 1
250 \fBCommit Data (ID: {C, D, A, T }) (N * (H + 16) bytes)\fR
261 The first H bytes are for the OID of the root tree\&.
272 The next 8 bytes are for the positions of the first two parents of the ith commit\&. Stores value 0x70000000 if no parent in that position\&. If there are more than two parents, the second value has its most\-significant bit on and the other bits store an array position into the Extra Edge List chunk\&.
283 The next 8 bytes store the topological level (generation number v1) of the commit and the commit time in seconds since EPOCH\&. The generation number uses the higher 30 bits of the first 4 bytes, while the commit time uses the 32 bits of the second 4 bytes, along with the lowest 2 bits of the lowest byte, storing the 33rd and 34th bit of the commit time\&.
288 .nr an-no-space-flag 1
292 \fBGeneration Data (ID: {G, D, A, 2 }) (N * 4 bytes) [Optional]\fR
303 This list of 4\-byte values store corrected commit date offsets for the commits, arranged in the same order as commit data chunk\&.
314 If the corrected commit date offset cannot be stored within 31 bits, the value has its most\-significant bit on and the other bits store the position of corrected commit date into the Generation Data Overflow chunk\&.
325 Generation Data chunk is present only when commit\-graph file is written by compatible versions of Git and in case of split commit\-graph chains, the topmost layer also has Generation Data chunk\&.
330 .nr an-no-space-flag 1
334 \fBGeneration Data Overflow (ID: {G, D, O, 2 }) [Optional]\fR
345 This list of 8\-byte values stores the corrected commit date offsets for commits with corrected commit date offsets that cannot be stored within 31 bits\&.
356 Generation Data Overflow chunk is present only when Generation Data chunk is present and atleast one corrected commit date offset cannot be stored within 31 bits\&.
361 .nr an-no-space-flag 1
365 \fBExtra Edge List (ID: {E, D, G, E}) [Optional]\fR
372 This list of 4\-byte values store the second through nth parents for
373 all octopus merges\&. The second parent value in the commit data stores
374 an array position within this list along with the most\-significant bit
375 on\&. Starting at that array position, iterate through this list of commit
376 positions for the parents until reaching a value with the most\-significant
377 bit on\&. The other bits correspond to the position of the last parent\&.
385 .nr an-no-space-flag 1
389 \fBBloom Filter Index (ID: {B, I, D, X}) (N * 4 bytes) [Optional]\fR
400 The ith entry, BIDX[i], stores the number of bytes in all Bloom filters from commit 0 to commit i (inclusive) in lexicographic order\&. The Bloom filter for the i\-th commit spans from BIDX[i\-1] to BIDX[i] (plus header length), where BIDX[\-1] is 0\&.
411 The BIDX chunk is ignored if the BDAT chunk is not present\&.
416 .nr an-no-space-flag 1
420 \fBBloom Filter Data (ID: {B, D, A, T}) [Optional]\fR
431 It starts with header consisting of three unsigned 32\-bit integers:
441 Version of the hash algorithm being used\&. We currently support value 2 which corresponds to the 32\-bit version of the murmur3 hash implemented exactly as described in
442 \m[blue]\fBhttps://en\&.wikipedia\&.org/wiki/MurmurHash#Algorithm\fR\m[]
443 and the double hashing technique using seed values 0x293ae76f and 0x7e646e2 as described in
444 \m[blue]\fBhttps://doi\&.org/10\&.1007/978\-3\-540\-30494\-4_26\fR\m[]
445 "Bloom Filters in Probabilistic Verification"\&. Version 1 Bloom filters have a bug that appears when char is signed and the repository has path names that have characters >= 0x80; Git supports reading and writing them, but this ability will be removed in a future version of Git\&.
456 The number of times a path is hashed and hence the number of bit positions that cumulatively determine whether a file is present in the commit\&.
467 The minimum number of bits
469 per entry in the Bloom filter\&. If the filter contains
471 entries, then the filter size is the minimum number of 64\-bit words that contain n*b bits\&.
483 The rest of the chunk is the concatenation of all the computed Bloom filters for the commits in lexicographic order\&.
494 Note: Commits with no changes or more than 512 changes have Bloom filters of length one, with either all bits set to zero or one respectively\&.
505 The BDAT chunk is present if and only if BIDX is present\&.
510 .nr an-no-space-flag 1
514 \fBBase Graphs List (ID: {B, A, S, E}) [Optional]\fR
521 This list of H\-byte hashes describe a set of B commit\-graph files that
522 form a commit\-graph chain\&. The graph position for the ith commit in this
523 file\*(Aqs OID Lookup chunk is equal to i plus the number of commits in all
524 base graphs\&. If B is non\-zero, this chunk must exist\&.
536 H\-byte HASH\-checksum of all of the above\&.
541 .SH "HISTORICAL NOTES:"
543 The Generation Data (GDA2) and Generation Data Overflow (GDO2) chunks have the number \fI2\fR in their chunk IDs because a previous version of Git wrote possibly erroneous data in these chunks with the IDs "GDAT" and "GDOV"\&. By changing the IDs, newer versions of Git will silently ignore those older chunks and write the new information without trusting the incorrect data\&.
546 Part of the \fBgit\fR(1) suite