4 ms·
I really wouldn't call the Linux kernel a monorepo. Not compared to Microsoft keeping all of Windows in a single repo. The problems start when you can't clone
by beojan 8y ago
I really wouldn't call the Linux kernel a monorepo. Not compared to Microsoft keeping all of Windows in a single repo.
The problems start when you can't clone the repo within an hour or so, because git doesn't allow partial clones like SVN did.
- WorldMaker 8y agoWhich is why Microsoft built GitVFS and has been contributing all sorts of interesting performance work to upstream git. Microsoft's devops work with Windows and the git transition is full of interesting blog posts and stories and metrics.
- CydeWeys 8y agoAll of the Linux source code is in a single repo. How is that not a monorepo? How are you defining monorepo if not this? The entire Windows codebase is also a monorepo. It just happens to be a bigger one.
- beojan 8y agoI'd define a monorepo as multiple loosely (or un-) coupled projects in the same repository. The Linux kernel is a single strongly coupled project. Nevertheless, whether or not you should keep your code in a single repository is more a question of the sheer size of the repository than of whether the code logically belongs in the same place.
- CydeWeys 8y agoMakes sense. But yeah, even the total code of all projects combined at a startup isn't likely to get anywhere close to the scale of the Linux repo, so it's at least a good example of how far you can get with a single large git repo (regardless of the relatedness of the contents therein).