On 11/12/22 01:06, Joseph Myers wrote: > On Fri, 11 Nov 2022, Tobias Burnus wrote: > >> For /onlinedocs/, I concur that we want to have the old doc there as there >> are >> many >> deep links. Still, we should consider adding a disclaimer box to all former >> mainline >> documentation stating that this data is no longer updated + point to the new >> overview >> page + we could redirect access which goes directly to '..../<module>/' and >> not a (sub)html >> page to the new site, as you proposed. > > Note that if we do this, I think my previous comments (to keep the > unmodified files somewhere long-term outside the directory served by the > webserver, with an automated process for modifying headers, so that > modified versions of that process can be re-run in future if we have > further changes to apply to the added headers) apply to such old mainline > documentation just as to release documentation. >
Hello. So I in context of [1] and [2] we will have to move content in between files and thus newly taken URLs (from gcc.gnu.org/onlinedocs/$man and gcc.gnu.org/install) can get invalid. So Gerald, I'm suggesting a new url base gcc.gnu.org/docs that will be filled with the new manuals and gcc.gnu.org/onlinedocs/$man and gcc.gnu.org/install locations should point to older (trunk) manuals (prev folder at server I guess). Having that, the new manuals will not available through navigation and will get some time for further changes. Thanks. Martin [1] https://gcc.gnu.org/pipermail/gcc/2022-November/239922.html [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107634
