Re: how does "clone --filter=sparse:path" work?

> > Should we simply be disallowing sparse:path filters over upload-pack?
> 
> The option to allow an absolute path over the wire probably needs more
> thought as you suggest.
> 
> Having it in the traverse code was useful for local testing in the
> client.
> 
> But mainly I was thinking of a use case on the client of the form:
> 
>     git rev-list
>         --objects
>         --filter=spec:path=.git/sparse-checkout
>         --missing=print
>         <commit>
> 
> and get a list of the blobs that you don't have and would need before
> you could checkout <commit> using the current sparse-checkout definition.
> You could then have a pre-checkout hook that would bulk
> fetch them before starting the actual checkout.  Since that would be
> more efficient than demand-loading blobs individually during the
> checkout.  There's more work to do in this area, but that was the idea.
> 
> But back to your point, yes, I think we should restrict this over the
> wire.