5 ms·
The article is really impressive. It's nice to see GitHub contribute changes back to the git project, and to know that the two work closely together.
by WayToDoor 5y ago
The article is really impressive. It's nice to see GitHub contribute changes back to the git project, and to know that the two work closely together.
- slver 5y agoIt's in their mutual interest. Imagine what happens to GIThub if GIT goes out of fashion.
- infogulch 5y agoYes, isn't it nice when interests of multiple parties are aligned such that they help each other make progress towards their shared goals?
- slver 5y agoWell, it's nice to see they're rational, indeed.
- jackbravo 5y agoOther rational companies could try to fix this without contributing upstream. Doing it upstream benefits competitors like gitlab. So yeah! It's nice seeing this kind of behavior
- slver 5y agoFirst, they not only contributed upstream, upstream developers contributed to this patch. I.e. they got help outside GitHub to make this patch possible. Second, if they had decided to fork Git, then they'd have to maintain this fork forever. Third, this fork could overtime become visibly or even worse subtly incompatible with stock Git which is still the Git running on GitHub users' machines, and both should interact with each other in 100% compatible manner. So, in this case, not contributing upstream was literally no-go. The only rational choice would be to not fork Git.