index-format: discuss recursion of cache-tree better
The end of the cache tree index extension format trails off with ellipses ever since 23fcc98 (doc: technical details about the index file format, 2011-03-01). While an intuitive reader could gather what this means, it could be better to use "and so on" instead. Really, this is only justified because I also wanted to point out that the number of subtrees in the index format is used to determine when the recursive depth-first-search stack should be "popped." This should help to add clarity to the format. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Derrick Stolee committed
Jan 7, 2021 at 16:32 UTC
4bdde337f40c089fea8e076eb00132fc093ca79e
1 file changed
+2
-1
Documentation/technical/index-format.txt
+2
-1
@@ -195,7 +195,8 @@ Git index format
195
first entry represents the root level of the repository, followed by the
196
first subtree--let's call this A--of the root level (with its name
197
relative to the root level), followed by the first subtree of A (with
198
- its name relative to A), ...
198
+ its name relative to A), and so on. The specified number of subtrees
199
+ indicates when the current level of the recursive stack is complete.
200
201
=== Resolve undo
202