Git was literally designed for kernel development.
That jumped out to me too. Seems incredible that the reason the system exists at all, has become a "weird" way to use it. You can git clone the kernel just like any other repo on github, so no big deal.
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.
Imagine telling the guy who invented the tool that he's using the tool wrong
Git, not github.
YouTube Can Never Support Kernel Development Discussions: How About A Blog Post?
Git was literally designed for kernel development.
That jumped out to me too. Seems incredible that the reason the system exists at all, has become a "weird" way to use it. You can git clone the kernel just like any other repo on github, so no big deal.
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.
Imagine telling the guy who invented the tool that he's using the tool wrong
Git, not github.
YouTube Can Never Support Kernel Development Discussions: How About A Blog Post?
Here is an alternative Piped link(s):
https://piped.video/MQ-mPhMA7XI
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Wonder if Forgeo will tackle any of this.
Does Forgejo have implemented federation yet?
I don't think so. I really should follow their bug for it. I've been following the NodeBB implementation and they seem to be getting close.
Old News