Adding more files to the revlog layer sounds like a move in the wrong direction and the motivation here seems quite weak too. Please discuss this with an actual plan on the mailing list.

I don't understand the motivation for this change.

I don't understand this change. We already support none as compression method.

This adds a penalty for the non-inline case?

I'm not sure that this is an improvement. We discussed whether we want to hard-wire the version even stricter ("exactly version 11"), especially because it is hard to predict when the output is going to change again.

Already merged as d55b71393907

Merged as 8d2b62d716b0

Merged as 77e73827a02d

Delayed for now as it doesn't work with the broken changelog.files and needs more efficient manifest logic first.

In D10082#157382, @marmoute wrote:

Do you have any performance number for that update ? for example the time we need to do that full some known large repositories, and the impact on a clone ?

In D10082#157189, @marmoute wrote:

What happens in the stream clone case ? Or during the transition from older to newer client ? streaming content from an older clone will not contains a fully up to date cache, and existing repository neither. How are we dealing with this ?
You mention the need to update the cache after stripping, but I don't see such change in the code. am I missing something ?

Superseded by D10280 and D10290

Superseded by D10290

Superseded by D10290

Superseded by D10290

Superseded by D10290

Superseded by D10290

Superseded by D10290

D10226 adds a separate packaging note about zstd.