Use-case:

• As a contributor, I submit a patchset to a mailing-list
• I am asked to revise the patchset
• I submit an updated version of said patchset
• With the proposed change: I see my old patchset's status changed from PROPOSED or NEEDS_REVISION to SUPERSEDED.

lists.sr.ht may also reply to the old patchset with content as below, to document the connection between said patchesets:

Superseded by: https://lists.sr.st/<~owner>/<list>/<message-id-of-latest-patch>

This is an alternative to implementing superseded use-case of https://todo.sr.ht/~sircmpwn/lists.sr.ht/193.

Parts of this have been discussed in public mumble meeting of January, 2022.