[llvm-dev] Git Move: GitHub+modules proposal

Mehdi Amini via llvm-dev llvm-dev at lists.llvm.org
Tue Jun 28 08:47:44 PDT 2016

> On Jun 28, 2016, at 1:55 AM, NAKAMURA Takumi via llvm-dev <llvm-dev at 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.


> On Tue, Jun 28, 2016 at 1:13 AM Renato Golin via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> On 27 June 2016 at 17:03, Rafael Espíndola <rafael.espindola at gmail.com <mailto:rafael.espindola at 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-dev at lists.llvm.org <mailto:llvm-dev at 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-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/20160628/003cc5f0/attachment.html>

More information about the llvm-dev mailing list