Re: What's cooking in git.git (May 2019, #05; Thu, 30)

From: Junio C Hamano <gitster@pobox.com>
Date: May 31, 2019, 18:56 UTC
Message-ID: <xmqqwoi6v4ei.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <nycvar.QRO.7.76.6.1905311346170.44@tvgsbejvaqbjf.bet>

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

Show 13 quoted lines

>> * cc/list-objects-filter-wo-sparse-path (2019-05-29) 1 commit
>>   (merged to 'next' on 2019-05-30 at 5a294203ad)
>>  + list-objects-filter: disable 'sparse:path' filters
>>
>>  Disable "--filter=sparse:path=<path>" that would allow reading from
>>  paths on the filesystem.
>>
>>  Will cook in 'next'.
>
> Not sure whether we want to fast-track this into v2.22.0. There is a risk.
>
> But then, the longer we ship with `--filter=sparse:path` *enabled*, the
> more we invite users to actually try and use it.

This one I wasn't quite decided on, for exactly the same reason why you said "Not sure". I am inclined to merge it to 'master' at this point, as it indeed is a risk to keep it enabled.

The only remaining question it raises is if it makes it worthwhile to add another rc; it introduces one new localizable string, too.

Thanks.