search for: _especially

...rkflow so that they eventually become LLVM contributors without noticing! > Indeed. The best way I think, all things considered, is that we have a single megarepo where everything LLVM is in there. That way in case anybody wants to make any changes to any part of it, it's a simpler process _especially compared to the status quo_. Cheers

On 29 Jul 2016, at 05:11, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > What I meant by “different problem" is that “downstream users” for instance don’t need to commit, that makes their problem/workflow quite different from an upstream developer (for instance it is fairly easy to maintain a read-only view of the existing individual git repo currently on

> On Jul 28, 2016, at 7:32 PM, Lang Hames <lhames at gmail.com> wrote: > > Hi Mehdi, > > This a narrow view IMO: the criteria #1 Chris mentioned to include projects in the monorepo was " must be tightly coupled to specific versions”. > It means that even with the test suite (and possibly some runtime) out of the monorepo, all the software that is tightly coupled