From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: "Pablo M. Ronchi" <pmronchi@yahoo.com.ar>,
"libstdc++" <libstdc++@gcc.gnu.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Links broken for C++ in web page "GCC online documentation: Latest releases"
Date: Sun, 16 May 2021 18:56:14 +0100 [thread overview]
Message-ID: <CAH6eHdSOtn=5MhqgJQrPoRs8cqSR-jU3EOhC5FDY8RFH=RBtLA@mail.gmail.com> (raw)
In-Reply-To: <627cad5-33ca-6b87-d84f-24a2f06e854a@pfeifer.com>
On Sun, 16 May 2021, 13:31 Gerald Pfeifer, <gerald@pfeifer.com> wrote:
> On Wed, 28 Apr 2021, Pablo M. Ronchi via Gcc wrote:
> > https://gcc.gnu.org/onlinedocs/
> >
> > under the subheadings:
> >
> > Latest releases
> > GCC 11.1 manuals:
> >
> > The following items have all their links broken (HTML,... tarball):
> >
> > ...
> > GCC 11.1 Standard C++ Library Manual (also in PDF or XML or an HTML
> tarball)
> > GCC 11.1 Standard C++ Library Reference Manual (also in PDF or XML GPL
> or XML
> > GFDL or an HTML tarball)
> > ...
>
> Thank you for your report, Pablo. Can you confirm this is working
> for you now?
>
It always takes a few hours to generate the libstdc++ docs after a release.
Longer if I forget about it.
They were missing immediately after the release, they're not now.
>
> The one link that is (still) broken for me is
> "XML GFDL" for the "GCC 11.1 Standard C++ Library Reference Manual"
>
That one is missing for every release and I have no idea how it's meant to
get created.
next prev parent reply other threads:[~2021-05-16 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <193d8071-0017-de33-4655-aeced7f43c46.ref@yahoo.com.ar>
[not found] ` <193d8071-0017-de33-4655-aeced7f43c46@yahoo.com.ar>
2021-05-16 11:54 ` Gerald Pfeifer
2021-05-16 17:56 ` Jonathan Wakely [this message]
2021-06-07 13:38 kerenyi&qwertynet hu
2021-06-15 15:09 Pablo M. Ronchi
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='CAH6eHdSOtn=5MhqgJQrPoRs8cqSR-jU3EOhC5FDY8RFH=RBtLA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=libstdc++@gcc.gnu.org \
--cc=pmronchi@yahoo.com.ar \
/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).