[llvm-dev] Add more projects into Git monorepo

Mehdi AMINI via llvm-dev llvm-dev at lists.llvm.org
Mon May 8 12:56:58 PDT 2017


Hi Takumi,

I understood you wanted to add projects in the repo, but I didn't get from
the email below that the existing master llvm-projects.
This is not great since this was used by some people as a day-to-day
development repo and is still documented on the getting started page!

-- 
Mehdi


2017-05-01 7:27 GMT-07:00 NAKAMURA Takumi via llvm-dev <
llvm-dev at lists.llvm.org>:

> 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 ?
>   For consistency, I could create a new repo.
>   But I think I can overwrite branches, since I assume this is read-only.
>
> Thanks, Takumi
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170508/e5120ef8/attachment.html>


More information about the llvm-dev mailing list