> At the other extreme Google has (mostly) a monorepo. One shouldn't conflate the VCS with org structure and/or code sharing. The Google monorepo is perforce-

> At the other extreme Google has (mostly) a monorepo. One shouldn't conflate the VCS with org structure and/or code sharing. The Google monorepo is perforce-based, which has per-branch, per-directory (even per-file) access control. One project's dependency on another can just as easily use the build artifacts from that other project as it can a source tree. And the way Google has built it, is looks far far closer to git than what you might think of with p4 (or svn or vss or name-your-monorepo). Lastly, AIUI, from day one there were very restricted parts of the "monorepo" that only a very few devs had access to. The Google monorepo is very different than a single git repo.