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.

  • demesisx
    link
    fedilink
    English
    arrow-up
    32
    arrow-down
    2
    ·
    edit-2
    1 year ago

    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 :

    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.

    • Spore@lemmy.ml
      link
      fedilink
      arrow-up
      19
      ·
      edit-2
      1 year ago

      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.

      • demesisx
        link
        fedilink
        English
        arrow-up
        10
        ·
        1 year ago

        I, for one, was quite ignorant of that fact.

      • Oliver Lowe@lemmy.sdf.org
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        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/

        • Spore@lemmy.ml
          link
          fedilink
          arrow-up
          21
          ·
          edit-2
          1 year ago

          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.

          • demesisx
            link
            fedilink
            English
            arrow-up
            10
            ·
            1 year ago

            Thanks for the insight. I’ll edit my comment to point to yours.

          • MigratingtoLemmy@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            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

            • Spore@lemmy.ml
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              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.

              • MigratingtoLemmy@lemmy.world
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                Ah, you mean email being used as a direct alternative to issue reports? I get it now, and TBH this makes intuitive sense. Thanks

    • rufus@discuss.tchncs.de
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      edit-2
      1 year ago

      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.

      • kureta@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Wh were you downvoted? You are correct.

        Git was originally authored by Linus Torvalds in 2005 for development of the Linux kernel, with other kernel developers contributing to its initial development. Since 2005, Junio Hamano has been the core maintainer.