4 ms·
FWIW, it’s not a git repo, it’s a mercurial repo.
by coder543 3y ago
FWIW, it’s not a git repo, it’s a mercurial repo.
- capitainenemo 3y agoAnd even if it was a git repo, seems this would still be a problem if everything wasn't on github. I guess the solution is to put all code on github...
- capitainenemo 3y agoBTW, for anyone reading this later, I asked some mercurial folks and putting an http cache in front of clones does indeed work just fine, although using the repo bundles is more performant (but might not be something you could ask folks to do). Given this repo seems fairly low activity (last commit 7 months ago) I doubt there'd be much of a problem with caching reads. Although given how they are using this repo, they'd probably be better off with a shallow clone, or a subversion proxy, or a snapshot tarball...likely just need a set of files..