3 ms·

It's a normal practice, google does it also: "The Google codebase includes approximately one billion files and has a history of approximately 35 million commits

• testUser69 10y ago
  >The Git community strongly suggests and prefers developers have more and smaller repositories. A Git-clone operation requires copying all content to one's local machine, a procedure incompatible with a large repository. They aren't copying all the files like you do with Git. They have a custom set up that sounds like it lets you checkout just the parts you need. I don't have time to read the whole thing, but it sounds like it works by breaking down a "super repo" into small "sub repos". This actually makes sense. There is no way working with a 300gb git repo is fun or efficient, and they've probably been doing that for years at Microsoft.
  • vertex-four 10y ago
    > I don't have time to read the whole thing, but it sounds like it works by breaking down a "super repo" into small "sub repos". They're explicitly not doing that. They have a massive, monolithic repo, and then tooling for interacting with that monolithic repo without having to grab the whole thing. They are not using Git. You just read the section titled "Alternatives".