https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36587
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Kaz Kylheku from comment #11) > The bug database has an "enhancement" type, so obviously, it is to be used > for submitting enhancements. No, it's for submitting enhancement *requests*, i.e. asking for or suggesting enhancements. Patches implementing those enhancements should be sent to the gcc-patches list, like all patches. > Why would you duplicate effort by implementing > a different process for tracking submissions? The process for submitting patches has always been to send them to the gcc-patches list for review, why would you duplicate effort by asking reviewers to also track patches in bugzilla? > In June 2008, when I submitted this, here is how the above Wiki page looked: > > https://gcc.gnu.org/wiki/GettingStarted?action=recall&rev=19 > > There is no mention of any special process at that time. There is still no "special process", the process for submitting patches is documented at https://gcc.gnu.org/contribute.html#patches and has always been to send them to the gcc-patches mailing list. That wiki page says nothing about attaching patches to bugzilla, but it does link to https://gcc.gnu.org/contribute.html which describes the patch submission process. Of course we welcome suggestions for enhancements, especially if they come with patches implementing the suggestion (that's the best kind! :-) but the process for submitting patches is to send them to the mailing list (and there are also legal prerequisites to be met, as described at the link above). If you're not interested in submitting the patch through that process that's unfortunate. Maybe someone else will be interested enough to do so on your behalf, but that won't happen automatically. There is no way to go through bugzilla and find patches posted here that were never sent via the correct process (there are thousands of attachments in bugzilla, some are testcases, some are patches that don't work, some are patches which were committed after being sent to the mailing list, some are patches that were superseded by improved patches sent to the list ... there is no way to automatically process them and find the ones that were never dealt with).
