Re: [PATCH v2 0/4] rm: integrate with sparse-index

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 8, 2022, 19:01 UTC
Message-ID: <xmqqczdasgp4.fsf@gitster.g>
In-Reply-To: <9ae61888-f7eb-0b36-8ed6-cf72104efb9d@github.com>

Victoria Dye <vdye@github.com> writes:

> This test failure is a result of a behavior change in the logging of 'git
> rm' in this series when removing a sparse directory. Patch 4 talks about it
> in more detail [1]; I failed to account for it in my series.

Ah, OK. When a directory being "git rm"'ed is outside the cone(s) of our interest, it indeed does feel like a waste to expand the index only to report which paths in that directory are being removed. It would be OK for the behaviour to be different inside and outside the cone(s).

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