>Automatic linking between related issues and pull requests (with backreferences)
Both are planned
>The request is itself a git branch, which makes it easy to compare both the current state of the request to master, as well as see incremental changes to the request as individual commits. I'm not sure how to accomplish that in a mailing list.
Not planned, but you can pretty trivially do this yourself. Just git checkout -b test-branch before applying the commits locally.
>Ability to search by tags/labels
Already there, kind of. You can search by the patch prefix, which is generally used to indicate the subproject. This is also supported outright on tickets, for which it's arguably a lot more useful.
> Just git checkout -b test-branch before applying the commits locally.
I guess that works, but it is a few more steps than clicking on a link. And if you are actively working on the project, it means you have to either switch branches or make a new workspace.
>Ability to subscribe to individual pull requests
>Automatic linking between related issues and pull requests (with backreferences)
Both are planned
>The request is itself a git branch, which makes it easy to compare both the current state of the request to master, as well as see incremental changes to the request as individual commits. I'm not sure how to accomplish that in a mailing list.
Not planned, but you can pretty trivially do this yourself. Just git checkout -b test-branch before applying the commits locally.
>Ability to search by tags/labels
Already there, kind of. You can search by the patch prefix, which is generally used to indicate the subproject. This is also supported outright on tickets, for which it's arguably a lot more useful.