https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64271
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Roland Illig from comment #12) > It should not be the job of a bug reporter to understand all the > internal workflows and actually commit the patches in the end. "Send the patch to the mailing list" does not mean "understand all the internal workfloats and actually commit the patches in the end", where do you get that idea? Patch review (and discussion, approval etc.) happens on the mailing lists, not in bugzilla. Reviewers do not scour bugzilla looking for patch submissions, they expect patches to be submitted to the mailing lists. That doesn't mean we don't want patches. It means we want patches to be submitted to one place (not bugzilla, not twitter, not reddit, not github). > Could someone perhaps check these patches and apply them as far as they make > sense? At least the ctype_base patches are still required for making GCC > 9.2.0 compile on x86_64--netbsd. Again, they should be sent to the relevant mailing lists. For libstdc++ patches that means gcc-patches and libstdc++.
