From: Mark Wielaard <mark@klomp.org>
To: Eli Zaretskii <eliz@gnu.org>, Marco Barisione <marco@barisione.org>
Cc: gdb@sourceware.org, overseers@sourceware.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: Broken documentation URLs
Date: Fri, 13 Oct 2023 15:08:35 +0200 [thread overview]
Message-ID: <a269e81012282160fdd8759ace0844809c3dcb33.camel@klomp.org> (raw)
In-Reply-To: <835y3au1fd.fsf@gnu.org>
Hi Eli,
On Fri, 2023-10-13 at 15:55 +0300, Eli Zaretskii wrote:
> > Recently, the GDB online documentation was moved from https://sourceware.org/gdb/onlinedocs/gdb/
> > to https://sourceware.org/gdb/current/onlinedocs/gdb.html/
That might have happened by a texinfo update?
> > As the old address worked for ages (at least a decade!),
> > there are a lot of links on the Internet pointing to some pages under the old URL, which are now broken.
> >
> > The search engines I tested by looking for “gdb.Value” (Google, Kagi and DuckDuckGo) haven’t updated their links either.
> > Is it possible to set up a redirect?
>
> Mark and the rest of overseers: can this be done, please?
As far as I know the onlinedocs are generated by the gdbadmin
through the /home/gdbadmin/ss/update-web-docs script.
See the /home/gdbadmin/ss/update-web-docs/HOWTO
I think this script would be responsible for creating a symlink or
redirect.
I just don't know what the official procedure is for updating that
script or how it is run (through a cronjob?)
Joel do you know?
Cheers,
Mark
next prev parent reply other threads:[~2023-10-13 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FCB7B3A0-3564-496D-A026-29B14F47230D@barisione.org>
2023-10-13 12:55 ` Eli Zaretskii
2023-10-13 13:06 ` Frank Ch. Eigler
2023-10-13 13:08 ` Mark Wielaard [this message]
2023-10-13 13:16 ` Mark Wielaard
2023-10-13 13:26 ` Marco Barisione
2023-10-28 16:13 ` Joel Brobecker
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=a269e81012282160fdd8759ace0844809c3dcb33.camel@klomp.org \
--to=mark@klomp.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=marco@barisione.org \
--cc=overseers@sourceware.org \
/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).