public inbox for
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <>
To: Sourceware Overseers ML <>
Cc: Bernhard Reutner-Fischer <>,
Subject: Web: inbox/gcc-bugs broken links (for all bugzilla mails)
Date: Thu, 13 Apr 2023 12:00:26 +0200	[thread overview]
Message-ID: <20230413120026.112fcfc1@nbbrfq> (raw)


When i direct my browser to
i get 404 for every link there.

ATM this renders to e.g.:
[Bug fortran/66973] New: Incorrect resolution of generic interface with TYPE(C_PTR)
 2023-04-12 18:48 UTC  (2+ messages)
` [Bug fortran/66973] "
href="">[Bug fortran/66973] New: Incorrect resolution of generic interface with TYPE(C_PTR)</a>
 2023-04-12 18:48 UTC  (2+ messages)
` <a
href="">[Bug fortran/66973]</a> &#34;

The first link yields a 404
and the second link likewise returns 404

Instead of the 404, i would have hoped to see the contents
of something like
for the first link
and for the second (probably)

Note that this 404 seems to happen to all bugzilla mails, e.g. in
there is "[Bug Infrastructure/29619] New: Setup gitolite for projects"
which points to
which also gives a 404.

PS: Currently we have an URL rewrite for for
    something like ^/PR([0-9]+) /bugzilla/show_bug.cgi?id=$1
    Could we please also support rewrites of lowercase "pr" for that's
    easier to type on virtual keyboards?


             reply	other threads:[~2023-04-13 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 10:00 Bernhard Reutner-Fischer [this message]
2023-04-13 20:27 ` Frank Ch. Eigler
2023-04-14  7:45   ` Bernhard Reutner-Fischer
2023-04-14 15:04     ` Frank Ch. Eigler
2023-04-16 19:34       ` Bernhard Reutner-Fischer
2023-04-17  9:07     ` Mark Wielaard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230413120026.112fcfc1@nbbrfq \ \ \ \

* 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).