> On Jun 28, 2016, at 1:55 AM, NAKAMURA Takumi via llvm-dev 
> <llvm-...@lists.llvm.org> wrote:
> 
> It has also submodules. 
> https://github.com/llvm-project/llvm-project-submodule 
> <https://github.com/llvm-project/llvm-project-submodule>
> 
> Both llvm-project(-tree) and (-submodule) have refs/notes/commits.

This is easy to compute when coming from SVN, the difficulty will be to keep 
this when having multiple git repo as a source.

— 
Mehid


> 
> On Tue, Jun 28, 2016 at 1:13 AM Renato Golin via llvm-dev 
> <llvm-...@lists.llvm.org <mailto:llvm-...@lists.llvm.org>> wrote:
> On 27 June 2016 at 17:03, Rafael Espíndola <rafael.espind...@gmail.com 
> <mailto:rafael.espind...@gmail.com>> wrote:
> > I think that trying to create a ordering/rev number between independent git
> > repositories is fundamentally unreliable.
> >
> > If we want to keep llvm and clang in lock step we should probably probably
> > just have them in the same repository like
> > https://github.com/llvm-project/llvm-project 
> > <https://github.com/llvm-project/llvm-project>.
> 
> That is similar to the proposal we have, except that llvm-projects
> will have sub-modules.
> 
> Having all of them in the same physical repository is a big problems
> for those that only use a small subset of the components, which is the
> vast majority of users, most of the time (all buildbots, Jenkins,
> local development, downstream users, even releases don't clone all
> repos).
> 
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-...@lists.llvm.org <mailto:llvm-...@lists.llvm.org>
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev 
> <http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
> _______________________________________________
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Reply via email to