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

[Filipe Cabecinhas via llvm-commits]

filcab added a subscriber: filcab.
filcab added a comment.

What about branches? I'm guessing we should expect the usual release branches. But will any person be able to create a branch? Will there be a policy, if this is the case? Is the policy enforceable?


================
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.
+
----------------
How easy will it be to clone the "aggregated" repo, and then get some (but not all) of the submodules?

================
Comment at: docs/Proposals/GitHub.rst:130
@@ +129,3 @@
+* 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.
+
----------------
I wouldn't call it broken.
Won't it have the same end result as having a checkout per project and simply updating them close to each other?

Basically, it won't be "any more broken" than using this method for updating:

```
#!/bin/bash
for dir in llvm/{,tools/{clang,lld},projects/{libcxx,libcxxabi,compiler-rt}}; do
  # (cd $dir && svn up) # for SVN
  (cd $dir && git checkout master && git pull) # for git
done
```


https://reviews.llvm.org/D22463