cc/list-objects-filter-wo-sparse-path, was Re: What's cooking in git.git (May 2019, #05; Thu, 30)
- Date: Fri, 31 May 2019 22:26:11 +0200 (CEST)
- From: Johannes Schindelin <Johannes.Schindelin@xxxxxx>
- Subject: cc/list-objects-filter-wo-sparse-path, was Re: What's cooking in git.git (May 2019, #05; Thu, 30)
On Fri, 31 May 2019, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes:
> >> * 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.
That'd be more a question to the L10N coordinator (who you Cc:ed)... Jiang
Lin? Would that require another -rc?