@fosskers I much prefer sending a patch than having to create a PR. The flexibility, which is what also brings the risk of making mistakes, is the crucial difference. Sending different patches in the same message or sending patches that depend on other patches are two examples of what the PR-workflow has difficulties expressing.
Also, if you make a mistake, no problem, just try again. People are willing to help (contract that to the silent no-message-no-response merge requests you sometimes see on GitHub, that feel so mechanic and impersonal).