public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: "Jonathan Wakely" <jwakely@redhat.com>,
	"Martin Liška" <mliska@suse.cz>,
	gcc@gcc.gnu.org
Subject: Re: Links to web pages are broken.
Date: Thu, 10 Nov 2022 17:58:16 +0100	[thread overview]
Message-ID: <C11F9ED0-3B26-4934-ADA3-F994BF615C2D@gmail.com> (raw)
In-Reply-To: <397083e0-8dc1-1931-306a-8517f2a4c72d@gjlay.de>



> Am 10.11.2022 um 17:45 schrieb Georg-Johann Lay <avr@gjlay.de>:
> 
> 
> 
>> Am 10.11.22 um 16:25 schrieb Jonathan Wakely:
>>> On Thu, 10 Nov 2022 at 15:23, Jonathan Wakely <jwakely@redhat.com> wrote:
>>> 
>>> On Thu, 10 Nov 2022 at 15:17, Georg-Johann Lay <avr@gjlay.de> wrote:
>>>> 
>>>> 
>>>> 
>>>> Am 10.11.22 um 16:05 schrieb Martin Liška:
>>>>> On 11/10/22 15:45, Georg-Johann Lay wrote:
>>>>>> Hi, I just observed that links like
>>>>>> 
>>>>>> https://gcc.gnu.org/install/configure.html
>>>>>> 
>>>>>> ceased to work.  Presumably this is to sphinx stuff, but it would be
>>>>>> great if not hundreds of links across the web to GCC pages like the
>>>>>> above would be 404.
>>>>>> 
>>>>>> I know that the new link is
>>>>>> 
>>>>>> https://gcc.gnu.org/install/configuration.html
>>>>>> 
>>>>>> but that doesn't help with existing pointers.
>>>>>> 
>>>>>> "Deep" links like https://gcc.gnu.org/install/configuration.html#avr
>>>>>> 
>>>>>> won't work either, so all reasonable anchors have been ditched, too?
>>>>>> 
>>>>>> Johann
>>>>> 
>>>>> Hello.
>>>>> 
>>>>> We're working on that and we'll create a redirection:
>>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107610
>>>>> 
>>>>> Thanks for pointing out.
>>>>> 
>>>>> Martin
>>>> 
>>>> Ok thanks, I left a note there.
>>> 
>>> The second part of your note about deep links into the new docs is a
>>> completely separate issue. That can't be fixed with HTTP redirects for
>>> the old URLs.
>> And there are still anchors, they're just different:
>> https://gcc.gnu.org/install/configuration.html#cmdoption-with-avrlibc
>> Now there are anchors to every single option, which is much better
>> than it used to be.
> 
> Yes, its nice.  But existing links are still invalidated.  Just take some tutorial that explains how to set up gcc, where you want to provide references that are point-on and not just "gcc.gnu.org".
> 
> Does this also mean that "deep" links to onlinedocs won't work any more?

How about moving the new docs to
onlinedocs-new/ and simply keeping the old
Doc tree around?  Re-using the old dir looks like a mistake in hindsight?

Richard 

> Johann
> 
> 

  reply	other threads:[~2022-11-10 16:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 14:45 Georg-Johann Lay
2022-11-10 15:05 ` Martin Liška
2022-11-10 15:17   ` Georg-Johann Lay
2022-11-10 15:23     ` Jonathan Wakely
2022-11-10 15:25       ` Jonathan Wakely
2022-11-10 16:44         ` Georg-Johann Lay
2022-11-10 16:58           ` Richard Biener [this message]
2022-11-10 17:01             ` Jonathan Wakely
2022-11-11  8:48               ` Martin Liška
2022-11-11 12:14                 ` Georg-Johann Lay
2022-11-11 12:31                   ` Martin Liška

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=C11F9ED0-3B26-4934-ADA3-F994BF615C2D@gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=avr@gjlay.de \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely@redhat.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).