Ryan Gonzalez via llvm-dev
2017-May-08 21:23 UTC
[llvm-dev] Has anyone here considered using repo for the Git migration?
https://source.android.com/source/using-repo It plays well with large projects (heck, it was designed for Android), and it works really well. I'm guessing you guys have already considered it and rejecting it for some really smart reason, but I wanted to make sure! ;) -- Ryan (ライアン) Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else http://refi64.com/
André Jansen Medeiros Villar via llvm-dev
2017-May-09 03:39 UTC
[llvm-dev] Has anyone here considered using repo for the Git migration?
There's also jiri https://github.com/fuchsia-mirror/jiri 2017-05-08 18:23 GMT-03:00 Ryan Gonzalez via llvm-dev < llvm-dev at lists.llvm.org>:> https://source.android.com/source/using-repo > > > It plays well with large projects (heck, it was designed for Android), > and it works really well. > > I'm guessing you guys have already considered it and rejecting it for > some really smart reason, but I wanted to make sure! ;) > > -- > Ryan (ライアン) > Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else > http://refi64.com/ > _______________________________________________ > 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/20170509/a383ca64/attachment.html>
Mehdi AMINI via llvm-dev
2017-May-20 18:58 UTC
[llvm-dev] Has anyone here considered using repo for the Git migration?
2017-05-08 14:23 GMT-07:00 Ryan Gonzalez via llvm-dev < llvm-dev at lists.llvm.org>:> https://source.android.com/source/using-repo > > > It plays well with large projects (heck, it was designed for Android), > and it works really well. > > I'm guessing you guys have already considered it and rejecting it for > some really smart reason, but I wanted to make sure! ;) >Yes, it was considered, no-one really championed it at the time. Conceptually I personally don't see any difference with submodules, and in practice I don't see a killer difference. The main discussion has been focused on a "submodule" split-repo model vs a monorepo. -- Mehdi -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170520/60d0297e/attachment.html>
Ryan Gonzalez via llvm-dev
2017-May-20 19:33 UTC
[llvm-dev] Has anyone here considered using repo for the Git migration?
I'd say the main difference is ease-of-use. Submodules easily go out-of-sync, so you have to keep running 'git submodule update'. Sometimes you can accidentally push code in one without dependent code in the other. With repo, all that is automatic. 'repo up' will push all "submodules", 'repo sync' pulls from them all, etc. Code is based on branches, not isolated commits, so there's less confusion, and it's easy to change one part to one branch in order to test stuff while leaving the others intact. -- Ryan (ライアン) Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else http://refi64.com On May 20, 2017 1:58 PM, "Mehdi AMINI" <joker.eph at gmail.com> wrote: 2017-05-08 14:23 GMT-07:00 Ryan Gonzalez via llvm-dev < llvm-dev at lists.llvm.org>:> https://source.android.com/source/using-repo > > > It plays well with large projects (heck, it was designed for Android), > and it works really well. > > I'm guessing you guys have already considered it and rejecting it for > some really smart reason, but I wanted to make sure! ;) >Yes, it was considered, no-one really championed it at the time. Conceptually I personally don't see any difference with submodules, and in practice I don't see a killer difference. The main discussion has been focused on a "submodule" split-repo model vs a monorepo. -- Mehdi -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170520/467f4e1e/attachment.html>
Bruce Hoult via llvm-dev
2017-May-20 22:31 UTC
[llvm-dev] Has anyone here considered using repo for the Git migration?
"repo" doesn't automatically give you atomic commits across different modules. You can fake it when you need to by tagging all the modules, but that's a separate step. I hate it, and for our internal work on ART we throw the whole of AOSP into a single git repository anyway. On Sat, May 20, 2017 at 9:58 PM, Mehdi AMINI via llvm-dev < llvm-dev at lists.llvm.org> wrote:> > > 2017-05-08 14:23 GMT-07:00 Ryan Gonzalez via llvm-dev < > llvm-dev at lists.llvm.org>: > >> https://source.android.com/source/using-repo >> >> >> It plays well with large projects (heck, it was designed for Android), >> and it works really well. >> >> I'm guessing you guys have already considered it and rejecting it for >> some really smart reason, but I wanted to make sure! ;) >> > > Yes, it was considered, no-one really championed it at the time. > Conceptually I personally don't see any difference with submodules, and in > practice I don't see a killer difference. The main discussion has been > focused on a "submodule" split-repo model vs a monorepo. > > -- > Mehdi > > > > _______________________________________________ > 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/20170521/c1bb6b87/attachment.html>