SourceHut may not have the pull request method of Github, may deal pretty much only in plain text, but at least it doesn't abuse your data for money and for others to use. Oh and it's accessible.
@devinprater Honestly we're always a bit scared to use email for patches because it seems like it'd mess up the hash (different committer email on the importing side? I don't know how git does that, and why should it matter who imports it). Is it easier than it seems?
@IceWolf @devinprater
I did some testing on my own and found that when importing a patch from email with `git am`, the author email from the original commit is the one used for the applied commit, and the committer email will be from the config of whoever ran `git am`.
So in a sense, the local commit that was sent as a patch email and the one that's applied by the maintainer are different, even though their contents are the same. But from Git's perspective, they're the same, so doing a rebase won't introduce merge conflicts. Code authorship is preserved (though the author date is changed to the date of the email message by `git send-email`).
Good references are the manpages for `git format-patch`, `git send-email`, and `git am`.
@nleigh @devinprater Blorfh. So pulling commits around /is/ actually better (for the git history).
