search for: monorepository

...ls here: https://reviews.llvm.org/D24167 >> >> If you have some good reasons why you would think a proposal would be >> problematic to you, or one would better fit your workflow, feel free >> to expose them now. > > It could be problematic for us depending on how the monorepository is > structured. We reference the LLVM git repository directly and use it to > migrate to new versions, pick patches, etc. If LLVM proper were part of > a larger repository that becomes more difficult to do because the commit > file paths won't match. We'd be back to essentia...

...ect? > Yes > If so, that raises a number of questions for me that aren't directly > addressed in the document as far as I can see: > > 1. How are the individual component git mirrors going to be maintained? Just exactly as they are today. > > If a commit goes to the monorepository, what is going to extract the > relevant bits and commit them to the individual mirrors? The document > notes that with a monorepository a single commit can touch multiple > projects (that's good!) but something has to extract the parts of that > commit that are relevant to each su...

> On Sep 3, 2016, at 6:05 PM, Patrice Kouame <pkouame at mac.com> wrote: > > Someone mentioned llvm in a mono repository below… Right, we actually have a proposal to take what is in the current SVN repo here: http://llvm.org/svn/llvm-project/ and migrate this to a single repository. I was not sure if you were referring to this proposal (monorepo) or to the recent emails about