rengolin added inline comments. ================ Comment at: docs/Proposals/GitHub.rst:208 @@ +207,3 @@ +3. Make sure we have an llvm-project (with submodules) setup in the official + account, with all necessary hooks (history, update, merges). +4. Make sure bisecting with llvm-project works. ---------------- mehdi_amini wrote: > I'd like to see clearly mentioned somewhere else than in the plan that on top > of "hooks" hosted by github, we will need to maintain our own webservice on > our own server to answer updates from theses hooks and update the umbrella. > That's a non-negligible drawback in face of the motivation exposed in the > "Why move at all?" section. There are two types of hooks:
1. Pre-commit hooks that will stop anyone trying to merge/force push commits to the projects, in order to keep the history clean. These are install once, use forever. Zero maintenance after the initial period. 2. Post-commit hooks on the other projects / OR / external webservice/buildbot that will update the umbrella project like any existing Git mirror. Maintenance of this is either free (hooks) or very cheap (buildbot/cron jobs). On both cases, the history is preserved at least within the update cycle, which shouldn't be more than 5 minutes, and will be the update cycle that buildbots will pick the commits anyway. https://reviews.llvm.org/D22463 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
