public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: "Gerald Pfeifer" <gerald@pfeifer.com>, "Martin Liška" <mliska@suse.cz>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: old install to a different folder
Date: Fri, 11 Nov 2022 09:40:32 +0100	[thread overview]
Message-ID: <9cca5f24-881e-e46d-93e5-dc231ca7aa41@codesourcery.com> (raw)
In-Reply-To: <fcdd83f0-e634-16ef-a5fc-641c1f4c7736@pfeifer.com>

Hi Gerald,

On 10.11.22 20:24, Gerald Pfeifer wrote:
> On Thu, 10 Nov 2022, Martin Liška wrote:
>> We noticed we'll need the old /install to be available for redirect.
>>
>> Gerald, can you please put it somewhere under /install-prev, or
>> something similar?
> I'm afraid I am confused now. Based on your original request I had removed
> the original /install directoy.

I think we just need to handle more. Namely:

* Links directly to https://gcc.gnu.org/install/
   this works and shows the new page.

* Sublinks - those currently fail as the name has changed:
   https://gcc.gnu.org/install/configure.html (which is now https://gcc.gnu.org/install/configuration.html )
   https://gcc.gnu.org/install/build.html (now: https://gcc.gnu.org/install/building.html )
   https://gcc.gnu.org/install/specific.html#avrhttps://gcc.gnu.org/install/host-target-specific-installation-notes-for-gcc.html#avr

My impression is that it is sufficient to handle those renamings and we do not need the old pages.

However, others might have different ideas. Note that this was discussed in the thread "Links to web pages are broken."

Tobias

-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

  reply	other threads:[~2022-11-11  8:40 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 [this message]
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=9cca5f24-881e-e46d-93e5-dc231ca7aa41@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --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).