Skip to content

Commit e44b6df

Browse files
carlosmngitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 2579e1d commit e44b6df

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

Documentation/technical/index-format.txt

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -147,8 +147,9 @@ GIT index format
147147
- 160-bit object name for the object that would result from writing
148148
this span of index as a tree.
149149

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.
152153

153154
The entries are written out in the top-down, depth-first order. The
154155
first entry represents the root level of the repository, followed by the

0 commit comments

Comments
 (0)