How does this coverage hold up? It was a fun read from back in my highschool days, when I was still five years from trying Linux on my own AMD Thunderbird 1Ghz. It wasn’t until 2008 that I tried again and it stuck.
How does this coverage hold up? It was a fun read from back in my highschool days, when I was still five years from trying Linux on my own AMD Thunderbird 1Ghz. It wasn’t until 2008 that I tried again and it stuck.
Edit: my below comment was actually wrong. They actually do use git.
Thanks for sharing. What I find most interesting is that Linus is still using the same email-based software development methods for the kernel while the rest of the software engineering world has evolved to use his other invention, git, for that. I’m kind of second-hand embarrassed for those geniuses who have yet to adopt proper version control for (what I’d argue is) the most important project in the computing world.
Here’s a far more nuanced explanation from Spore’s reply to this comment :
Honestly I’m surprised that so many people don’t know how git can be used without those repository hosting sites. That’s one way to use it, not the only way. And it’s not even the way it was originally designed for.
Checkout git format-patch.
I, for one, was quite ignorant of that fact.
I’m not so surprised anymore. I’m self-taught using open-source software projects for guidance. But not everyone learns like that. For example in the commercial software dev world, having patches easy to apply with minimum tooling isn’t usually a priority (for better or worse).
This is actually a little story I had half written down; your comment prompted me to finish it. Thanks! https://www.srcbeat.com/2023/11/git-email/
What? Linux does use git for version control.
Is this article (and the many sources I see confirming it) inaccurate then?
https://www.theregister.com/AMP/2020/08/25/linux_kernel_email/
I’m happy to be wrong if you have any evidence to refute what I’ve written.
Ps. I’m talking about the kernel.
Git and Email are not mutually exclusive. In order to collaborate with git, you need and only need a way to send your commits to others. Commits can be formatted as plain-text files and sent through emails. That is how git has been used by its author from literally the first release of it.
Thanks for the insight. I’ll edit my comment to point to yours.
Could you explain? I’m still stuck with a mind-block, can’t imagine how a git server can track changes to code with messages from email
A git server don’t need to know email to work, and it is not required to have a git server. Email in this workflow is an alternative to a PR: contributor submit a set of commits to the maintainer (or anyone interested). Then the maintainer is free to apply or merge the commits. After that the code can be pushed to any servers.
Ah, you mean email being used as a direct alternative to issue reports? I get it now, and TBH this makes intuitive sense. Thanks
Yeah, that’s not quite right. You need a means to discuss things and review code. You can do this via a website or mailing list. The Linux kernel uses the latter. Lots of other devs use the former. Like Github. And Github and Git aren’t the same. The issue tracking, discussion platform etc are something Github does on top of Git. You can as well use Email or a different service/online platform for the communication. The actual program code is stored in Git in both cases.
You know that git is also Linus’ project, right?
deleted by creator
Wh were you downvoted? You are correct.