From: "Martin Liška" <mliska@suse.cz>
To: Tobias Burnus <tobias@codesourcery.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: old install to a different folder
Date: Fri, 11 Nov 2022 09:50:43 +0100 [thread overview]
Message-ID: <53a45315-0684-d0e8-c793-ff8630e77482@suse.cz> (raw)
In-Reply-To: <9cca5f24-881e-e46d-93e5-dc231ca7aa41@codesourcery.com>
On 11/11/22 09:40, Tobias Burnus wrote:
> However, others might have different ideas. Note that this was discussed in the thread "Links to web pages are broken."
Yes, please discuss this further in the aforementioned thread.
I do support the Richi's idea about using a new URL for the new Sphinx documentation
while keeping the older Texinfo documentation under /onlinedocs and /install
Martin
next prev parent reply other threads:[~2022-11-11 8:50 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 [this message]
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=53a45315-0684-d0e8-c793-ff8630e77482@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).