public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: p2242 - broken link in http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html
Date: Mon, 11 Dec 2023 07:47:22 +0000	[thread overview]
Message-ID: <CAH6eHdSS5ruSCXPT1zqwH9KNU3X0F2ZkDtojf1sSw_R7SHcYGQ@mail.gmail.com> (raw)
In-Reply-To: <bac8171e-d943-c8f7-5649-b446c09c5e4a@pfeifer.com>

[-- Attachment #1: Type: text/plain, Size: 940 bytes --]

On Mon, 11 Dec 2023, 01:34 Gerald Pfeifer, <gerald@pfeifer.com> wrote:

> http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html has a link to
> https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p2442r2.html .
>
> I'm quite sure this used to work, and the usual suspects for that site
> of changing ".html" to ".htm" or increasing "p2442r2" to "p2442r3" do not
> help.
>

That's unlikely to ever help, because if there is an r3 revision then there
must have been an r2 before it.

The best way to find the correct URL for the latest revision is the
redirect service: https://wg21.link/p2442
That says it's p2442r1.


> Now googling for 2442 finds a "downgrade" to "p2242r1" which does work:
>   https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p2442r1.html
>
> Should I update that docs accordingly? Or am I missing something?
>

Please update it. It looks like a copy & paste error from the previous
table row.

Thanks!

      reply	other threads:[~2023-12-11  7:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11  1:34 Gerald Pfeifer
2023-12-11  7:47 ` Jonathan Wakely [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=CAH6eHdSS5ruSCXPT1zqwH9KNU3X0F2ZkDtojf1sSw_R7SHcYGQ@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gerald@pfeifer.com \
    --cc=libstdc++@gcc.gnu.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).