git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Arguments for git update-index --refresh

From
Danny Lin <danny0838@gmail.com>
Date
Apr 15, 2022, 10:21 UTC
Message-ID
<CAMbsUu7fqECH1b7-POot0mD4kwmT0pzAMJrXznSPgv9wfv1OwA@mail.gmail.com>

According to the manual of git-update-index (https://git-scm.com/docs/git-update-index), --ignore-submodules must be passed before --refresh to take effect. However, a real test shows that -q and --ignore-missing also don't take effect when passed after --refresh. I wonder if --refresh must be passed after all other arguments, and the documentation may need a revision. I also wonder what is the reason that --refresh must be passed after, and can't we make it more flexible?

Next: Junio C Hamano
Message 1 of 2 in “Arguments for git update-index --refresh”
  1. Danny LinApr 15, 2022
  2. Junio C HamanoApr 15, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.