The Linux kernel is a very wierd project making use of external bug trackers, a mailing list, and a really odd way of using Git, it's no surprise that it's l...
Link is to a video of a guy reading somebody else’s blog? I guess that’s “content”…
Linus is using git the way he designed git to work… it’s a distributed source control system. Kernel development has always been about having lots and lots of “forks” which coordinate around a central “base.”
Was also designed to be accommodating of very diverse flows, like people living on remote islands with spotty internet connections, or people hacking on the kernel on long airplane trips without any connection, or people sending patches by email, or kernel maintainers acting as clearing houses for branches etc.
The famous “git flow” is only a tiny use case of what git is capable of, and Github (and other similar platforms) are mostly designed around those limitations and have otherwise very limited support for other flows.
Link is to a video of a guy reading somebody else’s blog? I guess that’s “content”…
Linus is using git the way he designed git to work… it’s a distributed source control system. Kernel development has always been about having lots and lots of “forks” which coordinate around a central “base.”
Was also designed to be accommodating of very diverse flows, like people living on remote islands with spotty internet connections, or people hacking on the kernel on long airplane trips without any connection, or people sending patches by email, or kernel maintainers acting as clearing houses for branches etc.
The famous “git flow” is only a tiny use case of what git is capable of, and Github (and other similar platforms) are mostly designed around those limitations and have otherwise very limited support for other flows.