While Pull Requests on GitHub or BitBucket are probably what most developers are used to these days, those came about after git and mercurial. Before GitHub, the norm was sending patches over email, which git and mercurial still support quite well and many projects prefer as the means of sharing patches. sourcehut is a new platform for hosting code which, among other things, is leveraging the email workflow for patches. The suggested workflow at sourcehut is to create a mailing list (which sourcehut can host) and users can then email patches to the list. A review takes place over email and eventually the patch is applied. There are some clear strengths to this:
Drew, the creator of sourcehut (among many other things), has written a blog post about this:
But assuming you have bought into this, one question is: how to apply patches? The mailing list functionality of sourcehut provides a link that one can import a change in from easily, for example:
hg import https://lists.sr.ht/path/to/the/patch
In the case of some of your author's repositories on sourcehut, they are on private mailing lists so that solution doesn't work because one has to be logged into sourcehut to the messages.
But, your author is a user of mu4e for email, and handling this is actually pretty easy. Once the patch you wish to apply is opened in mu4e, all you need to do is:
M-x cd RET /path/to/location/of/repo RET | hg import -
cdfunction in emacs.
|, mu4e will pipe the email through a command.
Now you can apply patches easily from public or private lists on sourcehut.