search for: ctrlp

...://github.com/jlebar/llvm-repo-tools [3] https://github.com/llvm-project/llvm-project/commit/38a6db646d8f43cd9d7cec6c0533e40946cd162f (which, embarrassingly, has a typo in the commit message) [4] http://jasonkarns.com/blog/subdirectory-checkouts-with-git-sparse-checkout/ [5] https://github.com/kien/ctrlp.vim [6] https://github.com/jlebar/ctrlp-py-matcher [7] https://github.com/Valloric/YouCompleteMe On Sun, Jul 31, 2016 at 12:06 AM, Justin Lebar <jlebar at google.com> wrote: >> And if it is, then the "only thing a monorepo gets you" isn't something that you need a monorep...

...>> [3] https://github.com/llvm-project/llvm-project/commit/38a6db646d8f43cd9d7cec6c0533e40946cd162f >> (which, embarrassingly, has a typo in the commit message) >> [4] http://jasonkarns.com/blog/subdirectory-checkouts-with-git-sparse-checkout/ >> [5] https://github.com/kien/ctrlp.vim >> [6] https://github.com/jlebar/ctrlp-py-matcher >> [7] https://github.com/Valloric/YouCompleteMe >> >> On Sun, Jul 31, 2016 at 12:06 AM, Justin Lebar <jlebar at google.com> wrote: >>>> And if it is, then the "only thing a monorepo gets you"...

...] https://github.com/llvm-project/llvm-project/commit/38a6db646d8f43cd9d7cec6c0533e40946cd162f >>> (which, embarrassingly, has a typo in the commit message) >>> [4] http://jasonkarns.com/blog/subdirectory-checkouts-with-git-sparse-checkout/ >>> [5] https://github.com/kien/ctrlp.vim >>> [6] https://github.com/jlebar/ctrlp-py-matcher >>> [7] https://github.com/Valloric/YouCompleteMe >>> >>> On Sun, Jul 31, 2016 at 12:06 AM, Justin Lebar <jlebar at google.com> wrote: >>>>> And if it is, then the "only thing a mon...

> And if it is, then the "only thing a monorepo gets you" isn't something that you need a monorepo to get. This is an *extremely important* point to understand, so let me try to be really clear about the current state of the world and the state of the world under the two "move to git" proposals. Today, all commits ultimately end up in SVN. Our SVN is a effectively a

> The only thing a monorepo gets you that strictly isn’t possible without > it is the ability to commit to multiple projects in a single commit. > Personally I don’t think that is a big enough justification, but that is > my opinion, not a fact. Okay, I just bumped into r277008, in which commits to llvm, clang, and clang-tools-extra all have the same SVN revision number. I don't

Hi Duncan, > […] > 2. Those working on projects *outside* the monolithic repo will get the downsides of both: a monolithic repo that they are only using parts of, and multiple repos that are somehow version-locked. > > 3. For many (most?) developers, changing to a monolithic git repo is a *bigger* workflow change than switching to separate git repos. Many people (and at least some