From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [DOCS] sphinx: use new Sphinx links
Date: Thu, 10 Nov 2022 10:35:35 +0100 (CET) [thread overview]
Message-ID: <39fb5822-95aa-037a-5ac7-865e9096ff9f@pfeifer.com> (raw)
In-Reply-To: <8ae80e2a-9f49-4ebf-d7f0-815d32919573@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
On Thu, 10 Nov 2022, Martin Liška wrote:
>> What do you think of keeping the latest under this shorter and simpler
>> URL (too), though?
> Works for me.
:
>> I believe a symlink (in the file system) on gcc.gnu.org could pull that
>> off.
> Yep, please do so.
Done.
https://gcc.gnu.org/install/ is back with a new face.
Will you be reverting the link adjustments back from /onlinedocs/install/
to plain /install/ ?
>> 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.
> 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?
Yes, things have evolved historically and there was a time we
needed/wanted to treat /install especially, for example to retain
the same (white) background color across.
By now, if we are to make changes, we probably should rather make them
across all of /onlinedocs - favicon and our CSS being two such changes.
Not a critical priority, though, I guess.
Gerald
next prev parent reply other threads:[~2022-11-10 9:35 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
2022-11-10 9:35 ` Gerald Pfeifer [this message]
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=39fb5822-95aa-037a-5ac7-865e9096ff9f@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).