> You can git clone the repo to your local machine, and you can manually move it elsewhere, but there's no way to send a PR from your repo to mine

Have people forgotten that email exists?

▲ skydhash 4 days ago | parent | next [-]

For simple changes, you can just `git diff` it to a file, put that file on a pastebin and share that link with any communication tool (or share the file directly). `git format-patch` is more where you want to share the commits (message and all). And you're not tied to using email. It's just a collection of files that you can share using whatever.

▲

lloydatkinson 3 days ago | parent [-]

Is this a common usage? While I’ve only attempted to use patch files with a Git GUI, they have always failed with errors 100% of the time for me.

Given that Git GUIs just invoke Git, I don’t have a lot of faith in it.

	▲	skydhash 3 days ago \| parent \| next [-]
		The only Git Gui I've used extensively is magit, and patch worked fine. It's very much like cherry picking commit or doing merge. There can be conflict so be sure to use `--3way` flag.
	▲	SomeUserName432 3 days ago \| parent \| prev [-]
		Copy-as-patch in Intellij is great. Can easily apply minor changes, just sharing it over slack.

▲ edent 4 days ago | parent | prev | next [-]

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?

▲ layer8 4 days ago | parent | next [-]

If 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.

▲ 1718627440 4 days ago | parent | prev | next [-]

So 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.

▲ skydhash 4 days ago | parent | prev | next [-]

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.

▲ messe 4 days ago | parent | prev [-]

https://git-send-email.io/

▲ dogleash 4 days ago | parent | prev [-]

My email client (the default offering from my service provider ofc) is a POS. Therefore all of email is a miserable, failed tool and I can't believe you're being such a boomer rn.

▲

layer8 4 days ago | parent | next [-]

Use a better email client?

▲

esafak 4 days ago | parent | prev [-]

I can't tell if you're being sarcastic.

	▲	dogleash 4 days ago \| parent [-]
		I agree somewhere between 0% and 100% with the surface level message, and will give similar bounds for my agreement with the literal opposite of the text. It's a joke, not a manifesto in a joke suit.