From: "Martin Liška" <mliska@suse.cz>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [DOCS] sphinx: use new Sphinx links
Date: Thu, 10 Nov 2022 09:50:32 +0100 [thread overview]
Message-ID: <8ae80e2a-9f49-4ebf-d7f0-815d32919573@suse.cz> (raw)
In-Reply-To: <9c9b4969-dc72-a93b-335b-d72346bb437e@pfeifer.com>
On 11/10/22 09:28, Gerald Pfeifer wrote:
> Hi Martin,
>
> On Wed, 9 Nov 2022, Martin Liška wrote:
>> Gerald I would like to ask you for further server actions related
>> to the Sphinx documentation:
>
> sure, happy to help!
>
>> 1) https://gcc.gnu.org/install/ - for the future we will use
>> https://gcc.gnu.org/onlinedocs/install/
>
> That's a (fair) bit longer and more complex URL. I understand the point
> about cross referencing older GCC releases and see benefits with that.
>
> What do you think of keeping the latest under this shorter and simpler
> URL (too), though?
Hello.
Works for me.
>
> I believe a symlink (in the file system) on gcc.gnu.org could pull that
> off.
Yep, please do so.
>
>
>> So please remove content of /www/gcc/htdocs-preformatted/install
>
> That'll make some things simpler.
>
> Note how in style.mthml we have some special provisions for install/.
>
> Over the last years I have reduced those to a large extent. There is still
> a little bit post-processing going on right now including setting our CSS
> and our favicon.
>
> Should we see how to move those over to the new setup, or would you drop
> that?
Well, the entire content of gcc.gnu.org/onlinedocs/install/ is *one* of our
documentations and there should not be anything special about it.
Does it make sense?
Cheers,
Martin
>
> Gerald
next prev parent reply other threads:[~2022-11-10 8:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 11:13 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 [this message]
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
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=8ae80e2a-9f49-4ebf-d7f0-815d32919573@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).