Re: [PATCH v2 2/7] update-index: add --force-full-index option for expand/collapse test

From: Bagas Sanjaya <bagasdotme@gmail.com>
Date: Oct 6, 2021, 10:33 UTC
Message-ID: <f30504f5-e4a3-1b93-08dc-fb9137d36f65@gmail.com>
In-Reply-To: <f7cb9013d46731855c3ed42add62b021c0ad0c73.1633440057.git.gitgitgadget@gmail.com>

On 05/10/21 20.20, Victoria Dye via GitGitGadget wrote:

Show 7 quoted lines

> From: Victoria Dye <vdye@github.com>
> 
> Add a new `--force-full-index` option to `git update-index`, which skips
> explicitly setting `command_requires_full_index`. This lets `git
> update-index --force-full-index` run as a command without sparse index
> compatibility implemented, even after it receives sparse index compatibility
> updates.

`... explicitly setting ...` or `... explicitly set ...`? I thought of the latter.

-- 
An old man doll... just what I always wanted! - Clara

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