Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Restore the shallow clone behavior of the git walkers
Resolves trustification#775 I finally figured out how to update the shallow clone, setting the fetch depth to `i32::MAX` to signal infinite fetch depth, per https://git-scm.com/docs/shallow I had wrongly assumed depth=0 signaled infinite depth -- it does for an initial clone, but not an update of a shallow one. Essentially, this improves the "day 0" experience -- the first walk of the shallow clone takes no more than a few minutes. But the annoying ~30 minute fetch is deferred to the first update of the shallow clone, effectively turning it into a deep clone, after which subsequent fetches are fast. I think that's a workable compromise until libgit2's perf issue is addressed. Signed-off-by: Jim Crossley <[email protected]>
- Loading branch information