Yes. The only way to send patches without something like Github is over email. I don’t mind all the other stuff, but there’s no other way to do PRs than over email, and I hate email. I didn’t see that he gave alternatives. His preferred solution was an email
The formal PR button in a forge is a way to do that with one click, but a short email with all the same information is just as good.
Email isn’t “the only way” to send patches. In fact, he addresses that:
It doesn’t have to be by email, either. Any method of sending this data to the maintainer is fine. For example, I’m on Mastodon – so you could send me a repository URL via Mastodon if you really wanted to (provided you didn’t mind my responses being very short). Or you could send patches via any other communications medium that you and the maintainer are both on, if it lets you attach files to messages.
His preferred method is just sending a URL over email. You can use any communication method if you both already have an account.
Yes. The only way to send patches without something like Github is over email. I don’t mind all the other stuff, but there’s no other way to do PRs than over email, and I hate email. I didn’t see that he gave alternatives. His preferred solution was an email
Like, dawg, no it aint
They meant mail. With patches in punch cards. Just as good.
Email isn’t “the only way” to send patches. In fact, he addresses that:
His preferred method is just sending a URL over email. You can use any communication method if you both already have an account.