Rewriting RubyGems.org Git History

Obviously I&#x27;m not in their place, but in hindsight, my first thought when reading their initial issue was &quot;Why not make a container that serves the minimal subset of Rubygems stuff necessary to bootstrap Rubygems, and use that as a source in the event that the main side died and needed to be kickstarted again.<p>Docker itself used a similar strategy for their build process: the recommended build process uses containers to build the Docker binary, so they made a precompiled binary available that was crafted &quot;the hard way&quot; that could then be used for running the saner build process.

It would be really helpful to go into some detail on the steps taken to clean up the git history.

The-other-good-DVCS-that-everyone-almost-forgot-about, Mercurial, has exactly two solutions to the problem of overly large repos which, I presume, contain a lot of BLOBs.<p>First is Streaming Clones[1], whereby Mercurial server just takes all the files from the repository and transmits them over the transport connection, significantly decreasing TTFB.<p>The second is Largefiles extension[2], which turns Mercurial into more of a CVCS, but allows for efficient storage and retrieval of large binary files.<p>[1]: <a href="https://hglabhq.com/blog/2014/6/20/working-with-mercurial-over-unreliable-connections" rel="nofollow">https:&#x2F;&#x2F;hglabhq.com&#x2F;blog&#x2F;2014&#x2F;6&#x2F;20&#x2F;working-with-mercurial-ov...</a> [2]: <a href="http://mercurial.selenic.com/wiki/LargefilesExtension" rel="nofollow">http:&#x2F;&#x2F;mercurial.selenic.com&#x2F;wiki&#x2F;LargefilesExtension</a>

I find it funny that the problem was they didn&#x27;t think enough people know about the `--depth 1` flag to git clone, so the solution is to use submodules (which far fewer people know how to use properly).