From: Marco Barisione <marco@barisione.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb@sourceware.org, overseers@sourceware.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: Broken documentation URLs
Date: Fri, 13 Oct 2023 14:26:05 +0100 [thread overview]
Message-ID: <B04C7432-754D-4D9B-8558-26CAC9CC49D4@barisione.org> (raw)
In-Reply-To: <628cc44b813aa1c808ae3d287b3019c91ea81c1b.camel@klomp.org>
On 13 Oct 2023, at 14:16, Mark Wielaard <mark@klomp.org> wrote:
>
> On Fri, 2023-10-13 at 15:08 +0200, Mark Wielaard wrote:
>> 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?
>
> I still like to know how this exactly works. But there is no urgency.
>
> Frank already fixed the "root cause" by adding an explicit redirect in
> the httpd conf.d.
>
> RedirectMatch permanent "/gdb/onlinedocs/gdb(.*)" "/gdb/current/onlinedocs/gdb.html$1"
>
> So the script doesn't need to be changed.
I would like to understand more as well to know which URL is the
canonical one that should be linked from other websites.
--
Marco Barisione
next prev parent reply other threads:[~2023-10-13 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 12:20 Marco Barisione
2023-10-13 12:55 ` Eli Zaretskii
2023-10-13 13:06 ` Frank Ch. Eigler
2023-10-13 13:08 ` Mark Wielaard
2023-10-13 13:16 ` Mark Wielaard
2023-10-13 13:26 ` Marco Barisione [this message]
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=B04C7432-754D-4D9B-8558-26CAC9CC49D4@barisione.org \
--to=marco@barisione.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=mark@klomp.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).