4 ms·

I remember reading awhile back that email was better suited than GitHub for large projects (eg. Linux). Wouldn't that still be the case with GitLab?

• tremon 9y ago
  Probably this link: http://blog.ffwll.ch/2017/08/github-why-cant-host-the-kernel.html http://blog.ffwll.ch/2017/08/github-why-cant-host-the-kernel... ? In that case, yes, that applies to GitLab too. The main problem is how GitHub and GitLab manage subprojects: GitLab forks are strictly hierarchical in how they manage pull requests and contributions (you can only submit patches from your repo to the single repo that you forked from). But that may not be an issue for per-package repositories like Debian has on alioth. Debian does not have a monotree like the Linux kernel, every (source) package is a standalone project so the same objection does not apply here.
  • ramosmd 9y ago
    For how GitLab deals with forks, this blog post may offer some insights: https://about.gitlab.com/2016/12/01/how-to-keep-your-fork-up-to-date-with-its-origin/ https://about.gitlab.com/2016/12/01/how-to-keep-your-fork-up... This doc may also help: https://docs.gitlab.com/ee/workflow/repository_mirroring.html https://docs.gitlab.com/ee/workflow/repository_mirroring.htm...
  • DouweM 9y ago
    Note that "you can only submit patches from your repo to the single repo that you forked from" is no longer true for GitLab starting with 10.1 (released October 22, see https://about.gitlab.com/2017/10/22/gitlab-10-1-released/#merge-requests-across-forks https://about.gitlab.com/2017/10/22/gitlab-10-1-released/#me...), and hasn't been true for GitHub for a while (perhaps forever).