Embed Notice

@david_chisnall @whitequark you could even stay backwards compatible by adopting some well-known syntax to put into the author fields that points to the in-tree author aliases file.

This likely wouldn’t completely solve the GDPR issue since you would still be able to access old versions of that author name mapping file, but you could even work around that by doing sparse checkouts and only keeping the latest version of that file.