From: Joseph Myers <joseph@codesourcery.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: "Richard Biener" <richard.guenther@gmail.com>,
"Martin Liška" <mliska@suse.cz>,
"Gerald Pfeifer" <gerald@pfeifer.com>,
gcc-patches@gcc.gnu.org
Subject: Re: old install to a different folder
Date: Sat, 12 Nov 2022 00:06:47 +0000 [thread overview]
Message-ID: <3e2afcc5-6775-59f9-d3c6-fbd034412e50@codesourcery.com> (raw)
In-Reply-To: <7022f9a2-5f20-34c2-7c15-c5c0f058bde1@codesourcery.com>
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.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-11-12 0:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 11:13 [DOCS] sphinx: use new Sphinx links Martin Liška
2022-11-09 11:22 ` Martin Liška
2022-11-09 13:49 ` Martin Liška
2022-11-10 8:28 ` Gerald Pfeifer
2022-11-10 8:50 ` Martin Liška
2022-11-10 9:35 ` Gerald Pfeifer
2022-11-10 9:39 ` Martin Liška
2022-11-10 10:03 ` Gerald Pfeifer
2022-11-10 10:36 ` Martin Liška
2022-11-10 10:36 ` Tobias Burnus
2022-11-12 9:30 ` Gerald Pfeifer
2022-11-12 19:12 ` Gerald Pfeifer
2022-11-10 15:37 ` old install to a different folder Martin Liška
2022-11-10 19:24 ` Gerald Pfeifer
2022-11-11 8:40 ` Tobias Burnus
2022-11-11 8:50 ` Martin Liška
2022-11-11 9:11 ` Tobias Burnus
2022-11-11 10:18 ` Richard Biener
2022-11-11 10:33 ` Martin Liška
2022-11-11 10:37 ` Tobias Burnus
2022-11-12 0:06 ` Joseph Myers [this message]
2022-11-13 19:43 ` Martin Liška
2022-11-14 1:21 ` Gerald Pfeifer
2022-11-14 3:14 ` Martin Liška
2022-11-09 22:13 ` [DOCS] sphinx: use new Sphinx links Gerald Pfeifer
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=3e2afcc5-6775-59f9-d3c6-fbd034412e50@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=mliska@suse.cz \
--cc=richard.guenther@gmail.com \
--cc=tobias@codesourcery.com \
/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: link
Be 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).