Re: [PATCH] cache-tree: do not lazy-fetch merge tree

2019-09-04 Thread Junio C Hamano
Jonathan Tan writes: > When cherry-picking (for example), new trees may be constructed. During > this process, Git constructs the new tree in a struct strbuf, computes > the OID of the new tree, and checks if the new OID already exists on > disk. However, in a partial clone, the disk check causes

Re: [PATCH] cache-tree: do not lazy-fetch merge tree

2019-09-04 Thread Jonathan Tan
> On 9/3/2019 3:42 PM, Jonathan Tan wrote: > > When cherry-picking (for example), new trees may be constructed. During > > this process, Git checks whether these trees exist. However, in a > > partial clone, this causes a lazy fetch to occur, which is both > > unnecessary (because Git has already c

Re: [PATCH] cache-tree: do not lazy-fetch merge tree

2019-09-03 Thread Derrick Stolee
On 9/3/2019 3:42 PM, Jonathan Tan wrote: > When cherry-picking (for example), new trees may be constructed. During > this process, Git checks whether these trees exist. However, in a > partial clone, this causes a lazy fetch to occur, which is both > unnecessary (because Git has already constructed