public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug web/109355] New: Add a text warning to old gcc online manual stating it is out of date Date: Fri, 31 Mar 2023 09:38:27 +0000 [thread overview] Message-ID: <bug-109355-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109355 Bug ID: 109355 Summary: Add a text warning to old gcc online manual stating it is out of date Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: web Assignee: unassigned at gcc dot gnu.org Reporter: jg at jguk dot org Target Milestone: --- Could old GCC documentation release HTML web pages have a text warning at the top making it clear the documentation is out of date? ie: "Warning: This GCC manual is not the latest online documentation <link>" eg searching for "gcc function attributes error" gives me: https://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc/Function-Attributes.html I noticed popular search engines often suggest out of date GCC docs, eg this one from 2012. So I manually browse to https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html Which is fine, I just find it myself, but it would be nice if there was a reminder at the top of each page, in case someone doesn't check the URL.
next reply other threads:[~2023-03-31 9:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-31 9:38 jg at jguk dot org [this message] 2023-03-31 11:14 ` [Bug web/109355] " pinskia at gcc dot gnu.org 2023-03-31 11:15 ` pinskia at gcc dot gnu.org 2023-03-31 11:30 ` redi at gcc dot gnu.org 2023-03-31 13:00 ` jg at jguk dot org 2023-03-31 18:02 ` joseph at codesourcery dot com 2023-03-31 19:59 ` xry111 at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-109355-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).