summaryrefslogtreecommitdiff
path: root/Documentation/technical
diff options
context:
space:
mode:
authorDerrick Stolee <dstolee@microsoft.com>2019-06-18 18:14:25 (GMT)
committerJunio C Hamano <gitster@pobox.com>2019-06-20 03:46:26 (GMT)
commit5c84b3396c73382eb49285b4e4bbb1bf82be3a9c (patch)
treec7a49e92ec1657183c5b51ddc4bde481d3a378f9 /Documentation/technical
parent3cbc6ed3ee02ab7c8254d51528ca75644c52d52d (diff)
downloadgit-5c84b3396c73382eb49285b4e4bbb1bf82be3a9c.zip
git-5c84b3396c73382eb49285b4e4bbb1bf82be3a9c.tar.gz
git-5c84b3396c73382eb49285b4e4bbb1bf82be3a9c.tar.bz2
commit-graph: load commit-graph chains
Prepare the logic for reading a chain of commit-graphs. First, look for a file at $OBJDIR/info/commit-graph. If it exists, then use that file and stop. Next, look for the chain file at $OBJDIR/info/commit-graphs/commit-graph-chain. If this file exists, then load the hash values as line-separated values in that file and load $OBJDIR/info/commit-graphs/graph-{hash[i]}.graph for each hash[i] in that file. The file is given in order, so the first hash corresponds to the "base" file and the final hash corresponds to the "tip" file. This implementation assumes that all of the graph-{hash}.graph files are in the same object directory as the commit-graph-chain file. This will be updated in a future change. This change is purposefully simple so we can isolate the different concerns. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/technical')
0 files changed, 0 insertions, 0 deletions