Linux kernel development happens on Git. In fact, Git was created for the Linux kernel. Maybe instead of Git you mean GitHub? I can't find a link now, but if I remember right there was a brief period when Linux kernel development had to move to GitHub. Maybe when kernel.org got hacked? Linus Torvalds didn't like the way that GitHub formatted merge commits [1] (from a later date, but I think it was the same issue).[1] https://lore.kernel.org/lkml/CAHk-=wjbtip559HcMG9VQLGPmkurh5...
dikei|2 years ago
https://github.com/torvalds/linux/pull/17#issuecomment-56546...
littlestymaar|2 years ago
Without involving github at all, you can use git directly to push branches to a remote repository and then have it be merged by the maintainers there, which leads to a workflow that's pretty similar to the one you have with github.
Instead, Linux is being worked on by exporting the (git) patches and sharing them on a mailing list, effectively not using a significant feature of git and leading to a very different workflow than the one everyone else is using (github users and others alike), so I still find the question legitimate.
dikei|2 years ago
Once configured, you can send a series of patches to the mailing list with a single git command, and with just another command apply a series of patches from the mailing list. It's actually quite efficient.
mr_sturd|2 years ago
[0] - https://github.com/torvalds/linux
dry_soup|2 years ago