Re: What's cooking in git.git (Dec 2016, #02; Mon, 12)

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 13, 2016, 16:13 UTC
Message-ID: <xmqqinqn6c41.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <alpine.DEB.2.20.1612131641291.23160@virtualbox>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 12 quoted lines

>>  While I think it would make it easier for people to experiment and
>>  build on if the topic is merged to 'next', I am at the same time a
>>  bit reluctant to merge an unproven new topic that introduces a new
>>  file format, which we may end up having to support til the end of
>>  time.  It is likely that to support a "prime clone from CDN", it
>>  would need a lot more than just "these are the heads and the pack
>>  data is over there", so this may not be sufficient.
>> 
>>  Will discard.
>
> You could mark it as experimental, subject to change, and merge it to
> `next` safely.

Are you planning, or do you know somebody who plans to use that code soonish? Otherwise I'd prefer to drop it---at this point, the series is merely "just because we can", not "because we need it to further improve this or that".