[llvm-dev] Add more projects into Git monorepo

David Chisnall via llvm-dev
2017-05-07T08:01:01Z

Is this intended to be the monorepo that eventually becomes the official repo,
because if so I strongly object to putting libunwind, libc++ and libc++abi in
it.  I have recently been working on bring-up for libc++ and libunwind on a new
platform and the integration of libunwind with the LLVM build system is already
annoying (you can’t build it unless you have a working C++ standard library
implementation for your target, even thought it’s a dependency for libc++),
having to have a complete LLVM checkout would be even more overhead.

David

> On 7 May 2017, at 08:07, NAKAMURA Takumi via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
>
> I have done just now. 5 repos added including debuginfo-tests.
> ATM, it includes 17 repos total.
>
> - Created the new repo;
https://github.com/llvm-project/llvm-project-20170507.git
>   Branches will come later.
> - The previous repository has a merge commit that includes new repo. It
will stick to r302363.
> - Submodule repo has been pushed with -f.
>
> Rebasing to new branch(es) will take a few minutes. Please be patient.
>
> Thanks, Takumi
>
> On Mon, May 1, 2017 at 11:27 PM NAKAMURA Takumi <geek4civic at
gmail.com> wrote:
> I am planing to add projects into
https://github.com/llvm-project/llvm-project in near future, possibly this week.
>
> Before doing that, I would like to ask users of it.
> 1st option is my preference in each paragraph. Let me know if you have
other suggestions.
>
> * What is added?
>   I will add; libunwind, llgo, openmp and parallel-libs.
>   May I also add debuginfo-tests?
>
> * Will inactive projects be dropped?
>   I won't do.
>
> * Where shall I push the new monorepo?
>   - Create a new repository, like llvm-project-201705XX, or *-(number of
repos)
>   - Push new branches into the current llvm-project.git as different branch
name, like master-201705XX.
>   - Force overwrite llvm-project.git/master. I won't do since I was
blamed when I tried in the last time.
>
> * When I migrate trunk to the new one, how the previous branches will be?
>   - Push a merge-commit to the new one. Its commit message will announce
the new repo.
>   - Leave.
>   - Update also previous branches as well. (I don't want to do)
>
> * What should be done regarding to
https://github.com/llvm-project/llvm-project-submodule ?