Re: [RFC PATCH v2 2/4] transport: do not list refs if possible

2018-10-06 Thread Junio C Hamano
Stefan Beller writes: > On Thu, Sep 27, 2018 at 12:24 PM Jonathan Tan > wrote: > >> >> +test_expect_success 'when dynamically fetching missing object, do not list >> refs' ' >> + cat trace && > > leftover debug cat? It does look that way.

Re: [RFC PATCH v2 2/4] transport: do not list refs if possible

2018-09-27 Thread Stefan Beller
On Thu, Sep 27, 2018 at 12:24 PM Jonathan Tan wrote: > > +test_expect_success 'when dynamically fetching missing object, do not list > refs' ' > + cat trace && leftover debug cat?

[RFC PATCH v2 2/4] transport: do not list refs if possible

2018-09-27 Thread Jonathan Tan
When all refs to be fetched are exact OIDs, it is possible to perform a fetch without requiring the remote to list refs if protocol v2 is used. Teach Git to do this. This currently has an effect only for lazy fetches done from partial clones. The change necessary to likewise optimize "git fetch "