<div dir="ltr">It has also submodules. <a href="https://github.com/llvm-project/llvm-project-submodule">https://github.com/llvm-project/llvm-project-submodule</a><br><br>Both llvm-project(-tree) and (-submodule) have refs/notes/commits.</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 28, 2016 at 1:13 AM Renato Golin via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 27 June 2016 at 17:03, Rafael Espíndola <<a href="mailto:rafael.espindola@gmail.com" target="_blank">rafael.espindola@gmail.com</a>> wrote:<br>
> I think that trying to create a ordering/rev number between independent git<br>
> repositories is fundamentally unreliable.<br>
><br>
> If we want to keep llvm and clang in lock step we should probably probably<br>
> just have them in the same repository like<br>
> <a href="https://github.com/llvm-project/llvm-project" rel="noreferrer" target="_blank">https://github.com/llvm-project/llvm-project</a>.<br>
<br>
That is similar to the proposal we have, except that llvm-projects<br>
will have sub-modules.<br>
<br>
Having all of them in the same physical repository is a big problems<br>
for those that only use a small subset of the components, which is the<br>
vast majority of users, most of the time (all buildbots, Jenkins,<br>
local development, downstream users, even releases don't clone all<br>
repos).<br>
<br>
cheers,<br>
--renato<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>