summaryrefslogtreecommitdiff
path: root/Documentation/technical/racy-git.txt
diff options
context:
space:
mode:
authorDerrick Stolee <dstolee@microsoft.com>2018-06-28 12:52:45 (GMT)
committerJunio C Hamano <gitster@pobox.com>2018-06-28 16:45:03 (GMT)
commita9aa3c09270698ef3c15ec20013bd5a1abae0dea (patch)
tree58ed4f00b0a8326687c276fdeb107ea2f0438c95 /Documentation/technical/racy-git.txt
parent7547b95b4fbb8591726b1d9381c176cc27fc6aea (diff)
downloadgit-a9aa3c09270698ef3c15ec20013bd5a1abae0dea.zip
git-a9aa3c09270698ef3c15ec20013bd5a1abae0dea.tar.gz
git-a9aa3c09270698ef3c15ec20013bd5a1abae0dea.tar.bz2
commit-graph: fix documentation inconsistencies
The commit-graph feature shipped in Git 2.18 has some inconsistencies in the constants used by the implementation and specified by the format document. The commit data chunk uses the key "CDAT" in the file format, but was previously documented to say "CGET". The commit data chunk stores commit parents using two 32-bit fields that typically store the integer position of the parent in the list of commit ids within the commit-graph file. When a parent does not exist, we had documented the value 0xffffffff, but implemented the value 0x70000000. This swap is easy to correct in the documentation, but unfortunately reduces the number of commits that we can store in the commit-graph. Update that estimate, too. Reported-by: Grant Welch <gwelch925@gmail.com> Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/technical/racy-git.txt')
0 files changed, 0 insertions, 0 deletions