[Bug web/109355] Add a text warning to old gcc online manual stating it is out of date

2023-03-31 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109355

Xi Ruoyao  changed:

   What|Removed |Added

 CC||xry111 at gcc dot gnu.org

--- Comment #6 from Xi Ruoyao  ---
(In reply to Jonny Grant from comment #4)
> (In reply to Andrew Pinski from comment #2)
> > Oh and the manual is not exactly out of date for that version of gcc. So the
> > text you have would be wrong.
> 
> Sorry, you're completely right.  A script could search for  and insert
> after:
> 
> Warning: This GCC manual is not the  href="https://gcc.gnu.org/onlinedocs/gcc-latest-stable-redirect;>latest GCC
> release

It would be wrong.  GCC 9.5 released after GCC 12.1, so GCC 12.1 was not the
"latest" GCC release on May 27, 2022.  But we absolutely didn't want people to
look at GCC 9.5 doc instead of 12.1.

[Bug web/109355] Add a text warning to old gcc online manual stating it is out of date

2023-03-31 Thread joseph at codesourcery dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109355

--- Comment #5 from joseph at codesourcery dot com  ---
As I mentioned in previous discussions of this idea: any implementation 
should *not* involve simply editing the old generated files in place; it 
needs to involve keeping an unmodified copy of those files (which it might 
not readily be possible to regenerate now with current Texinfo) and having 
a properly automated process that goes from the unmodified source to the 
modified version served on the website, with the ability to rerun a new 
version of that process at any time.

[Bug web/109355] Add a text warning to old gcc online manual stating it is out of date

2023-03-31 Thread jg at jguk dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109355

--- Comment #4 from Jonny Grant  ---
(In reply to Andrew Pinski from comment #2)
> Oh and the manual is not exactly out of date for that version of gcc. So the
> text you have would be wrong.

Sorry, you're completely right.  A script could search for  and insert
after:

Warning: This GCC manual is not the https://gcc.gnu.org/onlinedocs/gcc-latest-stable-redirect;>latest GCC
release

[Bug web/109355] Add a text warning to old gcc online manual stating it is out of date

2023-03-31 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109355

--- Comment #3 from Jonathan Wakely  ---
We could add server rules to insert a banner into the HTML on every page, but
it's not trivial.

You might be thinking of PR 65699.

[Bug web/109355] Add a text warning to old gcc online manual stating it is out of date

2023-03-31 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109355

--- Comment #2 from Andrew Pinski  ---
Oh and the manual is not exactly out of date for that version of gcc. So the
text you have would be wrong.

[Bug web/109355] Add a text warning to old gcc online manual stating it is out of date

2023-03-31 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109355

--- Comment #1 from Andrew Pinski  ---
There is another bug about adding a version to the manual pages. Thar would be
better. Touching old generated html files is not a good solution. Plus the
version is in the url.