https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70255
--- Comment #23 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to shatz from comment #22) > It sucks. The software can't be changed after release, for obvious reasons, > but docs are not software. > If it's impossible to change the policy about not fixing mistakes in docs, > then, may be, it is possible to add documentation errata? Once it is out there, we cannot change every possible copy of a released version. We can change the docs for future releases, but we do not make new releases just for small documentation changes, it has wait (like actual important bugs) for the normal release schedule: https://gcc.gnu.org/develop.html You can always use directly the SVN/Git version of one of the stable branches. If you wish to see more frequent releases or backport a particular change to a stable branch, I encourage you to take a more active role (which is the beauty of free software as opposed to proprietary): https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps We do what we can with the time that we have.
