3 ms·

Even if not many developers use an email-based workflow for their own work, I think it’s pretty well-known that the Linux kernel does.

• Tharkun 7y ago
  I suspect you're overestimating the number of developers who know or use Linux. Many developers use Git on Windows and don't know anything about Linux, let alone about the workflow of the kernel team.
  • snazz 7y ago
    While GitHub and its clones have taken over, Git was intended to be used with emailed patches. The Linux kernel is a good example of a project using Git that way. It’s reasonably common among mature projects and it’s really not that hard: https://git-send-email.io/ https://git-send-email.io/
  • u801e 7y ago
    The git project uses the same workflow for development that the Linux kernel does. That is, using a mailing list to submit and discuss commits before merging them into the maintainer's repository.
    • Tharkun 7y ago
      Sure. But many users of git don't know (or care) about the workflow of the git team. They know github. Maybe gitlab. Or bitbucket. They could go their entire development careers without ever sending a patch as an email, instead relying on feature branches and pull requests. This could be completely alien to them, and it seems wrong to downvote srg for pointing that out.
  • asveikau 7y ago
    git format-patch and git am are still very useful features, even if you're not Linus, not a Linux developer, or on Windows. Basically you can serialize your git history as patches, transmit them any way you like (including email), and seamlessly re-integrate them as fully complete git commits. I sometimes use this even when working only with myself, i.e. if I want to test a change on multiple machines before I'm ready to push. Then I can use normal git workflow to rebase, etc.