4 ms·
Your post as of my writing this comment makes it unclear: Is the code in this specific release written by GitHub, GitLab, or both?
by reificator 8y ago
Your post as of my writing this comment makes it unclear: Is the code in this specific release written by GitHub, GitLab, or both?
- Jarwain 8y agoIf I had to guess: Github added the feature to their platform, but it didn't go upstream. Gitlab sponsored the dev-hours to rewrite the feature and actually push it upstream
- avar 8y agoIt was written by GitHub, and has been used in their internal fork of git.git for a long time. The work of integrating it with upstream was sponsored by GitLab, since it's something they were interested in to save space. The feature isn't interesting except for those that run a GitHub-like setup. I.e. repositories with a fork network where clones & fetches can be expected to be served from any repository in the network. In those setups it can make a lot of difference.
- Already__Taken 8y agoWith gitlab-ce being ~500mb this must be a gigantic improvement for them.
- reificator 8y ago> It was written by GitHub, and has been used in their internal fork of git.git for a long time. The work of integrating it with upstream was sponsored by GitLab, since it's something they were interested in to save space. That makes it clear, thank you. My assumption was that GitLab was copying work done by GitHub. > The feature isn't interesting except for those that run a GitHub-like setup. Sure, doesn't mean I'm not interested.