I have realized that it would be real useful to know which fixinclude fixes are actually in use so that old cruft can get retired. Since nobody at all has direct access to all the actively maintained platforms, it makes it difficult to know. Therefore, it seems reasonable to me to jigger up some sort of automated email that could get automatically processed to let me know which fixes are actively being triggered. Consequently I propose adding some infrastructure to GCC that will construct an email that users may, at their option, actually send out. It would go to some yet-to-be-defined but well defined email address set up to automatically handle these reports. The full GCC build would, as a final step, look to see if there were any messages to be sent home. If so, it would construct the full message, including headers, and ask the person (or machine) doing the build to send the email.
If this sounds reasonable, and if someone sets up the "gcc-repo...@gcc.gnu.org" email address, then sometime in the next couple of months, I'll work up a patch that will do what I am suggesting here. Thank you. Regards, Bruce
