[PATCH] D22463: [RFC] Moving to GitHub Proposal: NOT DECISION!

[Renato Golin via llvm-commits]

rengolin added inline comments.

================
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.
----------------
mehdi_amini wrote:
> 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.
Good point. I added just a description to this topic, since this is covered elsewhere.

================
Comment at: docs/Proposals/GitHub.rst:174
@@ +173,3 @@
+us what's wrong and how to help them fix it.
+
+We also recommend people and companies to migrate to Git, for its many other
----------------
So, LNT migration plan could be:

1. Use GitHub's SVN view on llvm-proj-submods
2. Move to understand submods
3. Migrate all instances

Looks fairly orthogonal to me...


https://reviews.llvm.org/D22463