An advocacy piece for git's built-in email-based workflow using git format-patch and git send-email. Covers practical setup tips (sendemail config options, annotating patches, setting default recipients), how to review patches via inline bottom-posting replies, and how to apply patches with git am. Argues that email-driven development scales from small projects to the Linux kernel, and is more open, federated, and powerful than GitHub-style pull requests. Also introduces sr.ht as a platform that embraces this workflow while lowering the barrier for those less comfortable with raw email.
Sort: