[lldb-dev] [llvm-dev] GitHub anyone?

Mehdi Amini via lldb-dev lldb-dev at lists.llvm.org
Tue May 31 14:15:47 PDT 2016


> On May 31, 2016, at 2:07 PM, Tim Northover <t.p.northover at gmail.com> wrote:
> 
> On 31 May 2016 at 13:45, Mehdi Amini via lldb-dev
> <lldb-dev at lists.llvm.org> wrote:
>> Apparently I wasn't very clear: llvm and clang (and the others projects) would be simple decoupled, individual git repositories. You would be able to check them out however you want and commit to them individually.
>> There would be an extra "integration repository" on top that would only provide the service that tells "r12345 is llvm:36c941c clang:eaf492b compiler-rt:6d77ea5". This repository should be managed transparently by some server-side integration.
> 
> This actually sounds like a really good idea even if a full move to
> git gets blocked for some reason. It seems like it could be a fairly
> common requirement: I don't suppose you know of an existing script
> that could do it? If not, I may take a stab.

I don't know of a script that would update this automatically, but the Gerrit feature seems pretty close: https://gerrit-review.googlesource.com/Documentation/user-submodules.html ; and it is possible that some Android tooling exists around the repo tool: https://source.android.com/source/developing.html

I think it is fairly easy to setup tools that do that, it is harder to do it reliably (i.e. handle concurrent push in clang and llvm for instance), or what if the server-side script fails the update because of a network issue?  Maybe it is not very important and one commit won't be part of the "global numbering"? Alternatively the push can be "failed" in such cases?

-- 
Mehdi



More information about the lldb-dev mailing list