I've always stated that a PR-esque workflow can be built on top of email, rather than replacing an existing system with a new walled garden like GitHub did. Sou

I've always stated that a PR-esque workflow can be built on top of email, rather than replacing an existing system with a new walled garden like GitHub did. SourceHut is all about reaching out to the existing communities, and email is how git itself was designed to be used. In your sibling comment I pointed to a video which demos a new feature that allows you to prepare patchsets to be emailed in a manner which is very similar to preparing a GitHub pull request or GitLab merge request: https://sourcehut.org/blog/2019-10-15-whats-cooking-october-2019/ https://sourcehut.org/blog/2019-10-15-whats-cooking-october-... I've always been of the opinion that email works better for me, and I think that too many people write it off without giving it its fair chance, but I've also conceded that many people enjoy the web-based workflow and I've been working on tools to accomodate them.