On Thu, May 14, 2020 at 05:05:01PM -0400, Theodore Y. Ts'o wrote: > > > > I don't think it's a common workflow for someone to repeatedly clone > > linux.git. Automated processes like CI would be doing it, but they tend > > to blow away the local disk between jobs, so they are unlikely to > > benefit from any native git local cache for something like this (in > > fact, we recommend that people use clone.bundle files for their CI > > needs, as described here: > > https://www.kernel.org/best-way-to-do-linux-clones-for-your-ci.html). > > If the goal is a git local cache, we have this today. I'm not sure > this is what Caleb was asking for, though: Right, I think I misunderstood his request -- I'd assumed we were talking about local cache, whereas it's about server-side or proxy-side cache. I think something like git-caching-proxy would be a neat project, because it would significantly improve mirroring for CI deployments without requiring that each individual job implements clone.bundle prefetching. -K
