I scanned this, the usual mono/multi arguments. All made moot by BitKeeper's nested approach: http://mcvoy.com/lm/bkdocs/nested.html http://mcvoy.com/lm/bkdoc

I scanned this, the usual mono/multi arguments. All made moot by BitKeeper's nested approach: http://mcvoy.com/lm/bkdocs/nested.html http://mcvoy.com/lm/bkdocs/nested.html in an open source system http://bitkeeper.org http://bitkeeper.org What nested brings to the table is the semantics of a mono repo with the advantages of a multi repo. The whole thing walks in lockstep, if you have a 3 week old version of the kernel and you add in the testing component (subrepo) then you get the 3 week old version of the testing component, all lined up with the same heads in the same tip commit. I get it that git won but at least steal the ideas. Edit: BTW, bk has a bk fast-import that usually works (it doesn't like octopus merges but other than that....)