On 07/08/2026 16:13, Tobias Burnus wrote:
Richard Earnshaw via Sourceware Forge wrote:
Richard Earnshaw (rearnsha) <[email protected]> approved the changes:
This seems reasonable to me - it's simply reformatting information
already stored in the GCC repository.
OK, but please give it until Tuesday in case there are any last minute
objections.
I think it is by itself a good idea – but I am not sure "inactive_email"
is the right word. There is:
* Non-primary email addresses - like in my case, my private email.
Still valid and with FSF assignment, but my work email is my
primary one.
* Old email addresses due to company-name changes - still valid but
not used for new new emails. (I have one of those too.)
* Old email addresses - not valid any more, usually because of
changing companies.
I think inactive is fine for all of those, but we could also have
a non_primary one - esp. for some things, I might still use my
private email – which is would be more a non_primary_email than
inactive_email.
In addition to what Richard and Jakub said, I will soon post a bigger
patch with all the emails scraped.
There is no reasonable way to validate that each and every email out of
the more than 600 that I found for people in MAINTAINERS is active or not.
So the best I can do is add the emails as inactive and let interested
parties make changes as they see fit.
HTH
Claudio
Tobias
