Re: [PATCH 2/2] fetch-pack: do not check links for partial fetch

Jonathan Tan writes: > Our only definition (currently) for the "partial" fetch boundary is > whether an object in a promisor packfile (a packfile obtained from the > promisor remote) references it, so I think that checking for crossing a > "partial" fetch boundary does

Re: [PATCH 2/2] fetch-pack: do not check links for partial fetch

On Wed, 14 Mar 2018 14:55:31 -0700 Junio C Hamano wrote: > Jonathan Tan writes: > > > When doing a partial clone or fetch with transfer.fsckobjects=1, use the > > --fsck-objects instead of the --strict flag when invoking index-pack so > > that links

Re: [PATCH 2/2] fetch-pack: do not check links for partial fetch

Jonathan Tan writes: > When doing a partial clone or fetch with transfer.fsckobjects=1, use the > --fsck-objects instead of the --strict flag when invoking index-pack so > that links are not checked, only objects. This is because incomplete > links are expected when

[PATCH 2/2] fetch-pack: do not check links for partial fetch

When doing a partial clone or fetch with transfer.fsckobjects=1, use the --fsck-objects instead of the --strict flag when invoking index-pack so that links are not checked, only objects. This is because incomplete links are expected when doing a partial clone or fetch. Signed-off-by: Jonathan Tan