According to git-update-index manual page: > --cacheinfo <mode>,<object>,<path>--cacheinfo <mode> <object> <path> > Directly insert the specified info into the index. For backward > compatibility, you can also give these three arguments as three separate > parameters, but new users are encouraged to use a single-parameter form. So, my commits change every old-style entry in code to the new format. It's not entirely necessary, but it unifies --cacheinfo usage across the code. Vadim Sannikov (2): Unify `update-index --cacheinfo` usage Unify `update-index --cacheinfo` usage (tests) git-merge-one-file.sh | 6 +++--- git-mergetool.sh | 2 +- merge-recursive.c | 2 +- po/bg.po | 4 ++-- po/ca.po | 4 ++-- po/de.po | 4 ++-- po/el.po | 2 +- po/es.po | 4 ++-- po/fr.po | 4 ++-- po/git.pot | 2 +- po/it.po | 4 ++-- po/ko.po | 4 ++-- po/ru.po | 8 ++++++-- po/sv.po | 4 ++-- po/tr.po | 4 ++-- po/vi.po | 4 ++-- po/zh_CN.po | 4 ++-- po/zh_TW.po | 4 ++-- t/lib-submodule-update.sh | 2 +- t/t0028-working-tree-encoding.sh | 4 ++-- t/t1006-cat-file.sh | 2 +- t/t1010-mktree.sh | 2 +- t/t1050-large.sh | 2 +- t/t1450-fsck.sh | 4 ++-- t/t3600-rm.sh | 4 ++-- t/t5520-pull.sh | 2 +- t/t5526-fetch-submodules.sh | 18 +++++++++--------- t/t5531-deep-submodule-push.sh | 2 +- t/t6130-pathspec-noglob.sh | 2 +- t/t6430-merge-recursive.sh | 2 +- t/t7003-filter-branch.sh | 2 +- t/t7011-skip-worktree-reading.sh | 4 ++-- t/t7012-skip-worktree-writing.sh | 4 ++-- t/t7113-post-index-change-hook.sh | 2 +- t/t7406-submodule-update.sh | 4 ++-- t/t9350-fast-export.sh | 8 ++++---- t/test-lib-functions.sh | 2 +- 37 files changed, 73 insertions(+), 69 deletions(-) base-commit: 675a4aaf3b226c0089108221b96559e0baae5de9 Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-708%2Fvadim-vj%2Fcacheinfo-modern-format-v1 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-708/vadim-vj/cacheinfo-modern-format-v1 Pull-Request: https://github.com/gitgitgadget/git/pull/708 -- gitgitgadget
