commit-graph: remove Future Work section

The commit-graph feature began with a long list of planned benefits, most of which are now complete. The future work section has only a few items left. As for making more algorithms aware of generation numbers, some are only waiting for generation number v2 to ensure the performance matches the existing behavior using commit date. It is unlikely that we will ever send a commit-graph file as part of the protocol, since we would need to verify the data, and that is expensive. If we want to start trusting remote content, then that item can be investigated again. While there is more work to be done on the feature, having a section of the docs devoted to a TODO list is wasteful and hard to keep up-to-date. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Derrick Stolee committed Jun 12, 2019 at 06:29 UTC 10bd0be173b0ab9a9255fc15a768b2518d3eba57
1 file changed -17
Documentation/technical/commit-graph.txt
-17
@@ -127,23 +127,6 @@ Design Details
127 helpful for these clones, anyway. The commit-graph will not be read or
128 written when shallow commits are present.
129
130 -Future Work
131 ------------
132 -
133 -- After computing and storing generation numbers, we must make graph
134 - walks aware of generation numbers to gain the performance benefits they
135 - enable. This will mostly be accomplished by swapping a commit-date-ordered
136 - priority queue with one ordered by generation number. The following
137 - operations are important candidates:
138 -
139 - - 'log --topo-order'
140 - - 'tag --merged'
141 -
142 -- A server could provide a commit-graph file as part of the network protocol
143 - to avoid extra calculations by clients. This feature is only of benefit if
144 - the user is willing to trust the file, because verifying the file is correct
145 - is as hard as computing it from scratch.
146 -
130 Related Links
131 -------------
132 [0] https://bugs.chromium.org/p/git/issues/detail?id=8