Why Google Stores Billions of Lines of Code in a Single Repository (2016)

Re:Why Google Stores Billions of Lines of Code in a Single R... by flukus on Wednesday July 25, 2018 @04:47AM (#17607804)

In the former each project is a self contained unit and if I'm working on project B I can forget project A even exists, which is lovely caused I've got enough to deal with on B as is. Each project can be branched individually, the log of project B is not polluted with commits to project A, I can rebase and not get a bunch of commits I don't care about.

The later forces me to be aware of the entire universe in that repo.

[ Parent | on HN ]

Re:Why Google Stores Billions of Lines of Code in a Single R... by Too on Wednesday July 25, 2018 @07:03AM (#17608325)

In the later you can also forget project A exist. git log works in subdirectories out of the box and if you didn't touch any files in project A a rebase will be trivial without any merge conflicts. Branching is also free (unless you are still in the SVN stoneage that requires a copy of each file) so it doesn't matter if you branch the whole monorepo or just a single project.

[ Parent | on HN ]

Re:Why Google Stores Billions of Lines of Code in a Single R... by wcoenen on Wednesday July 25, 2018 @08:36AM (#17608749)

> unless you are still in the SVN stoneage that requires a copy of each file

Maybe you are thinking of CVS? In SVN, creating branches has always been cheap in both space and time.

[ Parent | on HN ]