If you send a v2, v3 etc. of a patch, the earlier versions should be marked as superseded in patchwork automatically; currently this is a manual process. Note that this is complicated somewhat by submitters sometimes updating patches individually instead of re-sending the whole series, forgetting to add v2 (or forgetting to increment), etc. We may not be able to handle everything, but if we can at least catch the common cases that would save a lot of manual marking.
Damien Lespiau is currently working on this; his WIP code is on github: https://github.com/dlespiau/patchwork
Paul: Given the fact that Damien is currently focused on other issues so most likely this won't make it to M3, are you ok with me moving it to 2.1?
No problem, I've moved it.
Corresponding github issue: https://github.com/dlespiau/patchwork/issues/61
Updating target milestone. This enhancement is being developed, but implementation will depend on Patchwork version update.
Updating target milestone to match that of Dependency.
Updating target milestone to match that of Dependency
Currently being tested under latest patchwork instance.
Patch sent to upstream: https://github.com/dlespiau/patchwork/pull/192
Fix has been successfully tested, waiting for upstream merge. I'm closing this bug now and will open a new bug to implement the fix in production either by updating Patchwork code from repository or pointing to the new staging instance.