PRs are public and email patches are receiver's inbox only, right?
When I'm assessing the merit of any given project, I'd want see if there's a backlog of PRs, right?
Do projects using email-patch workflows set up listservs for receiving patches?
Not necessarily. For a 'lone wolf' project that might be the case, but some projects have public mailing-list archives, e.g. https://lists.gnu.org/archive/html/lightning/
I think it would be necessary to do some manual copy+pasting, or else use custom scripts/tooling, to turn such mailing-list archive pages into patch files (for git apply) or mbox files (for git am).
PRs are public and email patches are receiver's inbox only, right?
When I'm assessing the merit of any given project, I'd want see if there's a backlog of PRs, right?
Do projects using email-patch workflows set up listservs for receiving patches?