Documentation: clarify the invalidated tree entry format
When the entry_count is -1, the tree is invalidated and therefore has not associated hash (or object name). Explicitly state that the next entry starts after the newline. Signed-off-by: Carlos Martín Nieto <cmn@elego.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Carlos Martín Nieto committed
Jul 26, 2011 at 14:27 UTC
e44b6df90cfd6ccbf35c3d147ff5a0e4e22fb17a
1 file changed
+3
-2
Documentation/technical/index-format.txt
+3
-2
@@ -147,8 +147,9 @@ GIT index format
147
- 160-bit object name for the object that would result from writing
148
this span of index as a tree.
149
150
- An entry can be in an invalidated state and is represented by having -1
151
- in the entry_count field.
150
+ An entry can be in an invalidated state and is represented by having
151
+ -1 in the entry_count field. In this case, there is no object name
152
+ and the next entry starts immediately after the newline.
153
154
The entries are written out in the top-down, depth-first order. The
155
first entry represents the root level of the repository, followed by the