From: "Vadim Sannikov via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Vadim Sannikov <vsj.vadim@gmail.com>
Subject: [PATCH 0/2] Update update-index --cacheinfo entries' format
Date: Mon, 24 Aug 2020 14:51:41 +0000 [thread overview]
Message-ID: <pull.708.git.1598280703.gitgitgadget@gmail.com> (raw)
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
next reply other threads:[~2020-08-24 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 14:51 Vadim Sannikov via GitGitGadget [this message]
2020-08-24 14:51 ` [PATCH 1/2] Unify `update-index --cacheinfo` usage Vadim Sannikov via GitGitGadget
2020-08-24 18:51 ` Junio C Hamano
2020-08-24 14:51 ` [PATCH 2/2] Unify `update-index --cacheinfo` usage (tests) Vadim Sannikov via GitGitGadget
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.708.git.1598280703.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=vsj.vadim@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).