4 == pack-*.pack files have the following format:
6 - A header appears at the beginning and consists of the following:
9 The signature is: {'P', 'A', 'C', 'K'}
11 4-byte version number (network byte order):
12 Git currently accepts version number 2 or 3 but
13 generates version 2 only.
15 4-byte number of objects contained in the pack (network byte order)
17 Observation: we cannot have more than 4G versions ;-) and
18 more than 4G objects in a pack.
20 - The header is followed by number of object entries, each of
21 which looks like this:
23 (undeltified representation)
24 n-byte type and length (3-bit type, (n-1)*7+4-bit length)
27 (deltified representation)
28 n-byte type and length (3-bit type, (n-1)*7+4-bit length)
29 20-byte base object name if OBJ_REF_DELTA or a negative relative
30 offset from the delta object's position in the pack if this
31 is an OBJ_OFS_DELTA object
34 Observation: length of each object is encoded in a variable
35 length format and is not constrained to 32-bit or anything.
37 - The trailer records 20-byte SHA-1 checksum of all of the above.
39 == Original (version 1) pack-*.idx files have the following format:
41 - The header consists of 256 4-byte network byte order
42 integers. N-th entry of this table records the number of
43 objects in the corresponding pack, the first byte of whose
44 object name is less than or equal to N. This is called the
45 'first-level fan-out' table.
47 - The header is followed by sorted 24-byte entries, one entry
48 per object in the pack. Each entry is:
50 4-byte network byte order integer, recording where the
51 object is stored in the packfile as the offset from the
56 - The file is concluded with a trailer:
58 A copy of the 20-byte SHA-1 checksum at the end of
59 corresponding packfile.
61 20-byte SHA-1-checksum of all of the above.
65 -- +--------------------------------+
66 fanout | fanout[0] = 2 (for example) |-.
67 table +--------------------------------+ |
69 +--------------------------------+ |
71 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
72 | fanout[255] = total objects |---.
73 -- +--------------------------------+ | |
75 index | object name 00XXXXXXXXXXXXXXXX | | |
76 table +--------------------------------+ | |
78 | object name 00XXXXXXXXXXXXXXXX | | |
79 +--------------------------------+<+ |
81 | | object name 01XXXXXXXXXXXXXXXX | |
82 | +--------------------------------+ |
84 | | object name 01XXXXXXXXXXXXXXXX | |
85 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
87 | | object name FFXXXXXXXXXXXXXXXX | |
88 --| +--------------------------------+<--+
89 trailer | | packfile checksum |
90 | +--------------------------------+
91 | | idxfile checksum |
92 | +--------------------------------+
98 1-byte size extension bit (MSB)
101 n-byte sizeN (as long as MSB is set, each 7-bit)
102 size0..sizeN form 4+7+7+..+7 bit integer, size0
103 is the least significant part, and sizeN is the
104 most significant part.
106 If it is not DELTA, then deflated bytes (the size above
107 is the size before compression).
108 If it is REF_DELTA, then
109 20-byte base object name SHA-1 (the size above is the
110 size of the delta data that follows).
111 delta data, deflated.
112 If it is OFS_DELTA, then
113 n-byte offset (see below) interpreted as a negative
114 offset from the type-byte of the header of the
115 ofs-delta entry (the size above is the size of
116 the delta data that follows).
117 delta data, deflated.
120 n bytes with MSB set in all but the last one.
121 The offset is then the number constructed by
122 concatenating the lower 7 bit of each byte, and
123 for n >= 2 adding 2^7 + 2^14 + ... + 2^(7*(n-1))
128 == Version 2 pack-*.idx files support packs larger than 4 GiB, and
129 have some other reorganizations. They have the format:
131 - A 4-byte magic number '\377tOc' which is an unreasonable
134 - A 4-byte version number (= 2)
136 - A 256-entry fan-out table just like v1.
138 - A table of sorted 20-byte SHA-1 object names. These are
139 packed together without offset values to reduce the cache
140 footprint of the binary search for a specific object name.
142 - A table of 4-byte CRC32 values of the packed object data.
143 This is new in v2 so compressed data can be copied directly
144 from pack to pack during repacking without undetected
147 - A table of 4-byte offset values (in network byte order).
148 These are usually 31-bit pack file offsets, but large
149 offsets are encoded as an index into the next table with
152 - A table of 8-byte offset entries (empty for pack files less
153 than 2 GiB). Pack files are organized with heavily used
154 objects toward the front, so most object references should
155 not need to refer to this table.
157 - The same trailer as a v1 pack file:
159 A copy of the 20-byte SHA-1 checksum at the end of
160 corresponding packfile.
162 20-byte SHA-1-checksum of all of the above.