http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54419
--- Comment #55 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-09-09 15:21:45 UTC --- (In reply to comments #53 and #54) > Please post the patch to the right list and I'll approve it, all libstdc++ > patches need to go to the libstdc++ list. > > I've tested the patch myself now, it's ok, please commit it asap (but in > future > remember to send patches to the libstdc++ list as well as gcc-patches, I could > have approved it sooner had I seen it) I'ld to make a few comments: (1) A new patch has been posted at http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00466.html to fix a typo in my email address. (2) Jack Howarth does not seem to be around. So if someone with write access care about ASAP, he(r)? may commit the last version. (3) Jack has posted five revisions of the patch: http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00409.html http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00416.html http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00421.html http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00465.html http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00466.html following the request made at http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00411.html http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00417.html http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00418.html http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00432.html followed by a last post http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00499.html AFAICT nobody has been asking to cross post to libstdc++. (4) Managing libstdc++ on a specific mailing list made sense when G++ was an optional component of GCC. Now that C++, hence libstdc++, is mandatory, I think this policy should be revised: - the final patch should be posted and approved on gcc-patc...@gcc.gnu.org; - the libstdc++ maintainers should be more careful: four bootstrap failures caused by a single commit is way to much; - the libstdc++ maintainers should be more responsive: more than ten days to fix a bootstrap failure on primary platforms is way too long.
