| commit | 891435d55da80ca3654b19834481205be6bdfe33 | |
| author | Derrick Stolee <dstolee@microsoft.com> | |
| Fri, 6 Apr 2018 19:09:32 +0000 (6 19:09 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 11 Apr 2018 01:47:16 +0000 (11 10:47 +0900) | ||
| tree | fddc1768c14c6567f7be5205bf808d8bae86981a | treesnapshot (tar.gz zip) |
| parent | 2d5792f0716605ff0059fe4b5c865d6821c0161e | commitdiff |
treewide: rename tree to maybe_tree
Using the commit-graph file to walk commit history removes the large
cost of parsing commits during the walk. This exposes a performance
issue: lookup_tree() takes a large portion of the computation time,
even when Git never uses those trees.
In anticipation of lazy-loading these trees, rename the 'tree' member
of struct commit to 'maybe_tree'. This serves two purposes: it hints
at the future role of possibly being NULL even if the commit has a
valid tree, and it allows for unambiguous transformation from simple
member access (i.e. commit->maybe_tree) to method access.
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Using the commit-graph file to walk commit history removes the large
cost of parsing commits during the walk. This exposes a performance
issue: lookup_tree() takes a large portion of the computation time,
even when Git never uses those trees.
In anticipation of lazy-loading these trees, rename the 'tree' member
of struct commit to 'maybe_tree'. This serves two purposes: it hints
at the future role of possibly being NULL even if the commit has a
valid tree, and it allows for unambiguous transformation from simple
member access (i.e. commit->maybe_tree) to method access.
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
24 files changed: