https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32497
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu.org,
| |tkoenig at gcc dot gnu.org
--- Comment #18 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Valeriy E. Ushakov from comment #16)
> Why do I have to go through this strange ritual of
> taking this patch out of gcc's own bugtracker and sending it to gcc's own
> list for proposed patches?
I am knowledge-free about this particular area, just wanted to make
some general comments.
Several reasons, some of them overlapping.
This is how gcc development operates. For a large project like gcc
with many volunteers, you need to have rules, and in general, people
should stick to them.
Posting to gcc-patches gives everybody a chance to look at patches
and speak up if they have any concerns or advice. Not very many
people read individual PRs.
Finally, it's a very good thing that you need approval from somebody.
Compilers are notoriously complex beasts, and regressions for some
corner case can creep in quite easily - less easily if somebody
else has a look.
Of course, another thing that can be done is to add a maintainer for
a particular area to the PR. I have done so with this.
