3 ms·
Sure. But then I have to copy that patch, hope my email client hasn't mangled it, upload it somewhere, run an arcane command. Do you not see how much easier so
by edent 1y ago
Sure. But then I have to copy that patch, hope my email client hasn't mangled it, upload it somewhere, run an arcane command.
Do you not see how much easier something like GH is?
- skydhash 1y agoYou 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 1y agoOK, 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 1y agoBut 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.
- messe 1y agohttps://git-send-email.io/ https://git-send-email.io/
- 1718627440 1y agoSo instead of: local$ git push upstream$ git fetch && git merge it becomes: local$ git format-patch local: open file picker for attachments. upstream: save as ... upstream$ git am That's not that much different in time and effort.
- layer8 1y agoIf you can’t trust you email client’s editor, just add the patch file as an attachment. About zero chance that your email client will mangle it. GitHub seems easier because you are used to its workflow — which isn’t always devoid of arcanum either.