Patches delivered to two mailing lists handled by patchwork

I need to look into the situation where the same patch is sent to two mls patchwork listens to, currently it creates two distinct Patch objects. Maybe that's fine, but maybe we want to consolidate them into a single patch object that the two projects share (which doesn't work currently because a patch is linked to a single project)