From: Georg-Johann Lay <avr@gjlay.de>
To: "Martin Liška" <mliska@suse.cz>,
"Jonathan Wakely" <jwakely@redhat.com>,
"Richard Biener" <richard.guenther@gmail.com>
Cc: gcc@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Links to web pages are broken.
Date: Fri, 11 Nov 2022 13:14:35 +0100 [thread overview]
Message-ID: <4efbb4d0-3f8f-48f0-cb65-a691bb0d634a@gjlay.de> (raw)
In-Reply-To: <829ffa99-bbd9-cf98-50bd-9575a22f20b1@suse.cz>
Am 11.11.22 um 09:48 schrieb Martin Liška:
> On 11/10/22 18:01, Jonathan Wakely wrote:
>> Maybe just "docs" or "trunkdocs" or "latestdocs" instead of
>> "onlinedocs-new", since that is (1) very long, and (2) will look silly
>> in ten years when it's not new and we need to add
>> onlinedocs-even-newer 😉
>
> I do support it, it would be probably nicer than the complicated Rewrite rule
> Jonathan prepared.
>
>>
>> Or even onlinedocs/latest/ for the new stuff, and leave the old stuff
>> there in onlinedocs/ (without linking to it) so that old links work.
>
> I think we should add a new HTML header to the older documentation
> saying that's legacy. Something one can see here:
> https://matplotlib.org/3.3.4/tutorials/index.html
>
> Martin
Why it's legacy?
If I want docs for v12.2, then I don't care whether its generated by
sphinx or texinfo.
Just using a different documentation system won't render the very
content legacy?
I think it's a good idea to keep the old docs under their known URLs.
BTW, also search results from search engines are all 404.
Johann
next prev parent reply other threads:[~2022-11-11 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 14:45 Georg-Johann Lay
2022-11-10 15:05 ` Martin Liška
2022-11-10 15:17 ` Georg-Johann Lay
2022-11-10 15:23 ` Jonathan Wakely
2022-11-10 15:25 ` Jonathan Wakely
2022-11-10 16:44 ` Georg-Johann Lay
2022-11-10 16:58 ` Richard Biener
2022-11-10 17:01 ` Jonathan Wakely
2022-11-11 8:48 ` Martin Liška
2022-11-11 12:14 ` Georg-Johann Lay [this message]
2022-11-11 12:31 ` Martin Liška
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=4efbb4d0-3f8f-48f0-cb65-a691bb0d634a@gjlay.de \
--to=avr@gjlay.de \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jwakely@redhat.com \
--cc=mliska@suse.cz \
--cc=richard.guenther@gmail.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).