You've got this the wrong way round. Someone hosts a mailing list and some "canonical" repo - e.g. Linus's Linux tree - authors post patches to the mailing list

You've got this the wrong way round. Someone hosts a mailing list and some "canonical" repo - e.g. Linus's Linux tree - authors post patches to the mailing list. If you want to see every patch ever submitted you subscribe to the mailing list, and your mail server holds a copy of them all. You can download archives of the mailing lists via public-inbox and suchlike. And when you want to work on it, you grab Linus's tree. The vast majority of Linux developers don't have their own publicly-accessible repository that you can pull from - they push patches to the mailing list. Various archives can host copies of the mailing lists (you can ask https://www.mail-archive.com https://www.mail-archive.com to do so for you), and the git repository can obviously be mirrored anywhere anyone who can clone it likes. Congratulations, you now have a globally mirrored, decentralised development process where the canonical repo and any patches submitted never disappear.