Skip to content

Commit e05aa68

Browse files
committed
update-index: there no longer is apply --index-info
Back when we removed `git apply --index-info` in 2007, we forgot to adjust the documentation for update-index that reads its output. Let's reorder the description of three formats to present the other two formats that are still generated by git commands before this format, and stop mentioning `git apply --index-info`. Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent 53f9a3e commit e05aa68

File tree

1 file changed

+6
-9
lines changed

1 file changed

+6
-9
lines changed

Documentation/git-update-index.txt

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -268,23 +268,20 @@ USING --INDEX-INFO
268268
multiple entry definitions from the standard input, and designed
269269
specifically for scripts. It can take inputs of three formats:
270270

271-
. mode SP sha1 TAB path
272-
+
273-
The first format is what "git-apply --index-info"
274-
reports, and used to reconstruct a partial tree
275-
that is used for phony merge base tree when falling
276-
back on 3-way merge.
277-
278271
. mode SP type SP sha1 TAB path
279272
+
280-
The second format is to stuff 'git ls-tree' output
281-
into the index file.
273+
This format is to stuff `git ls-tree` output into the index.
282274

283275
. mode SP sha1 SP stage TAB path
284276
+
285277
This format is to put higher order stages into the
286278
index file and matches 'git ls-files --stage' output.
287279

280+
. mode SP sha1 TAB path
281+
+
282+
This format is no longer produced by any Git command, but is
283+
and will continue to be supported by `update-index --index-info`.
284+
288285
To place a higher stage entry to the index, the path should
289286
first be removed by feeding a mode=0 entry for the path, and
290287
then feeding necessary input lines in the third format.

0 commit comments

Comments
 (0)