From: Joel Brobecker <brobecker@adacore.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
Marco Barisione <marco@barisione.org>,
gdb@sourceware.org, overseers@sourceware.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: Broken documentation URLs
Date: Sat, 28 Oct 2023 09:13:23 -0700 [thread overview]
Message-ID: <ZT0zIzYU1MB/VqOh@adacore.com> (raw)
In-Reply-To: <628cc44b813aa1c808ae3d287b3019c91ea81c1b.camel@klomp.org>
> 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
Correct.
> > 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?
It's a script inside a (hum) CVS repository. Typically, when I need
to make changes, I simply make them there, and then commit under CVS.
I don't really know why things changed. We're using texinfo provided
by the sourceware system, and according to a comment I inserted in
the script, it was version 6.5, and checking now things haven't change
as it's still version 6.5. The ss scripts themselves haven't changed
either, so it must be something in the binutils-gdb repository.
That would be my guess.
--
Joel
prev parent reply other threads:[~2023-10-28 16:13 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
2023-10-28 16:13 ` Joel Brobecker [this message]
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=ZT0zIzYU1MB/VqOh@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=marco@barisione.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).