Do you mean sending patches by email? The author for the article also despises them as suggest alternatives for collaboration where you do “pull request” by people giving you a link to their repo and branch name (like literally asking you to try pulling from their git repo), or sending git bundle files which get around a lot of the problems of trying to send patch files around.
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.
I wouldn’t mind doing a self-hosted git repo and only using cli if I didn’t have to also use email to do so.
Seriously the worst part. Email is a technology that should be left in the past. It’s just awful. There’s no good way to do email.
Do you mean sending patches by email? The author for the article also despises them as suggest alternatives for collaboration where you do “pull request” by people giving you a link to their repo and branch name (like literally asking you to try pulling from their git repo), or sending git bundle files which get around a lot of the problems of trying to send patch files around.
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