You can store the patch somewhere (pastebin, cloud drive), and send the link instead. Or attach them to the email. No need to directly use `git send-email` or copy it in the body of the email.

▲

edent 4 days ago | parent [-]

OK, but then I still have to do work to get that patch and integrate it into my existing systems.

I don't know if you've ever used GitHub, GitLab, or CodeBerg - but PRs just appear in a list there. I don't need to do any work. Very handy especially if they're big changes.

I can also leave comments on specific bits of code, rather than emailing someone.

	▲	skydhash 4 days ago \| parent [-]
		But that's require a web browser, dealing with 2fa, and I would probably still export the patch and apply it locally to test. Using email can be done on a potato system, using my email client, which already have my workflow automated. Replying someone takes even less effort than commenting.