Where I work, we have several dozen repos, on for each component, and are thinking about merging it into a monorepo soon. That will end up giving us a repo with

Where I work, we have several dozen repos, on for each component, and are thinking about merging it into a monorepo soon. That will end up giving us a repo with several different root commits. In fact, for at least one of our components, we've already done this. We had something that solved the same problem for a couple of different permutations of software versions and platforms. The person who had originally written it had used separate repos, with common code copied and pasted between them, and later on we merged the repos together and factored out the common code so that could be shared. So we already have at least one repo which has 4 root commits, I believe. Actually, I just checked and it has 7 root commits. I'd forgotten that we had also had similar problems that needed to be solved for some other software, and had some interns who had done those in separate repos as well, which also eventually got merged in to share all of the common code: $ git log --max-parents=0 --pretty="format:%h %cd %s" --date=short 666c0bf 2012-07-09 Initial tree. 528ca3a 2012-06-12 first commit 50f1b18 2012-06-12 first commit 86d66e0 2011-11-17 initial 76a7789 2011-03-21 initial commit 58f7afc 2010-05-20 initial deb50b7 2009-10-29 initial commit