Re: [PATCH v4 01/20] sparse-index: design doc and format update

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 28, 2021, 01:47 UTC
Message-ID: <xmqq8s68oxr4.fsf@gitster.g>
In-Reply-To: <20210326202940.GC2271@szeder.dev>

SZEDER Gábor <szeder.dev@gmail.com> writes:

Show 8 quoted lines

>> +To start, we use a new repository extension, `extensions.sparseIndex`, to
>> +allow inserting sparse-directory entries into indexes with file format
>> +versions 2, 3, and 4. This prevents Git versions that do not understand
>> +the sparse-index from operating on one, but it also prevents other
>> +operations that do not use the index at all.
>
> Why is this not a non-optional index extension?  ...
> This really should be a non-optional index extension.

Yeah, the index extension mechanism was designed with optional and required kinds because we wanted to support exactly a use case like this one.

Thanks for pointing it out.

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