mehdi_amini added a subscriber: mehdi_amini. ================ Comment at: docs/Proposals/GitHub.rst:122 @@ +121,3 @@ +of understanding the *sequence* in which commits were added by using the +``git rev-list --count hash`` or ``git describe hash`` commands. + ---------------- filcab wrote: > How easy will it be to clone the "aggregated" repo, and then get some (but > not all) of the submodules? I expect the umbrella repo to come with scripts for that.
================ Comment at: docs/Proposals/GitHub.rst:129 @@ +128,3 @@ +* The linear history can still be accessed in the (RO) submodule meta project. +* Individual projects' history will be broken (linear, but local), and we need + the umbrella project (using submodules) to have the same view as we had in SVN. ---------------- This sentence is not clear: "Individual projects' history will be broken", I don't see what's "broken". ================ Comment at: docs/Proposals/GitHub.rst:168 @@ +167,3 @@ +additional benefits. + +2. Which tools will stop working? ---------------- I think that's covered line 136-137. ================ Comment at: docs/Proposals/GitHub.rst:173 @@ +172,3 @@ +use LNT with the SVN-View, but it would be best to move it to Git once and for +all. + ---------------- I don't think so: LNT is not dependent on SVN history. It is dependent on a single revision number cross-repository and cross-branches. This is something that the umbrella projects "could" provide. ================ Comment at: docs/Proposals/GitHub.rst:198 @@ +197,3 @@ +3. Make sure we have an llvm-project (with submodules) setup in the official + account. +4. Make sure bisecting with llvm-project works. ---------------- Uh, this point is not clear: there will a need for us to maintain a "non-trivial" hook on our server to handle this. This is not fleshed out in this document. https://reviews.llvm.org/D22463 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
