3 ms·
Option C: Custom tooling built for the purpose of managing collections of repositories. It appears the main argument for monolithic repositories is that it imp
by jamesrom 11y ago
Option C: Custom tooling built for the purpose of managing collections of repositories.
It appears the main argument for monolithic repositories is that it improves developer productivity by giving the developer access to the entire organisation's codebase.
What a terrible hack to provide something that could be better managed with other tools. No DCVS is an island.
- cpeterso 11y agoThe Android team wrote the "repo" to manage multiple git repositories: https://source.android.com/source/developing.html https://source.android.com/source/developing.html
- stinos 11y agoThere's also the multiple repository tool 'mr' http://linux.die.net/man/1/mr http://linux.die.net/man/1/mr which adresses exactly the I don't want to waste time dealing with multiple commands to manage multiple repositories complaint of the author and moreover can do so for repositories using different version control systems. I've been using it for years mainly because I have a few repos shared between projects and jobs, and using one monolithic repo would mean having to copy those repos around. (At least AFAIK - or how else do people using one big repository use external projects?)