5 ms·
Why can't git push, when it encounters a `.git/shallow`, just ask the git server to fill in the remaining history by verifying the parent hashes the client can
by zero_shift 2y ago
Why can't git push, when it encounters a `.git/shallow`, just ask the git server to fill in the remaining history by verifying the parent hashes the client can send?
- TachyonicBytes 2y agoIt can, but that's another type of "shallow", or more exactly "not-deep" cloning, called blobless cloning [1]. There is also treeless cloning, with other tradeoffs, but much to the same effect. I found this[2] very enlightening. [1] https://github.blog/open-source/git/get-up-to-speed-with-partial-clone-and-shallow-clone/ https://github.blog/open-source/git/get-up-to-speed-with-par... [2] https://www.howtogeek.com/devops/how-to-use-git-shallow-clone-for-faster-repository-cloning/ https://www.howtogeek.com/devops/how-to-use-git-shallow-clon...