From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Joseph Myers <joseph@codesourcery.com>,
Tobias Burnus <tobias@codesourcery.com>,
Richard Biener <richard.guenther@gmail.com>,
gcc-patches@gcc.gnu.org, Andrew Pinski <pinskia@gmail.com>
Subject: Re: old install to a different folder
Date: Mon, 14 Nov 2022 02:21:48 +0100 (CET) [thread overview]
Message-ID: <5e7dcf3d-8805-f997-b94b-6394618b25c4@pfeifer.com> (raw)
In-Reply-To: <f864f72f-56cb-9f3f-6eb0-33038798ee6f@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On Sun, 13 Nov 2022, Martin Liška wrote:
> 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.
I feel I may be missing something.
Why don't we
(1a) keep /onlinedocs for all docs < GCC 13,
(1b) possibly introduce /docs as an alternative URL (though we need
to keep /onlinedocs for all the existing ones),
(2) add sphinx docs for trunk, GCC 13 and later to /docs (and at the
same time /onlinedocs which is just an alias)
(3) put current installation documentation under /install and simply
add a few redirects for those pages that have changed names?
That way we can retain existing structures, possibly replace /onlinedocs
for the shorter /docs, and have one consistent index for all manuals.
Gerald
next prev parent reply other threads:[~2022-11-14 1:21 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
2022-11-13 19:43 ` Martin Liška
2022-11-14 1:21 ` Gerald Pfeifer [this message]
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=5e7dcf3d-8805-f997-b94b-6394618b25c4@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=mliska@suse.cz \
--cc=pinskia@gmail.com \
--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).