From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Sourceware Overseers ML <overseers@sourceware.org>
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>, aldot@gcc.gnu.org
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)
Hi!
When i direct my browser to
https://inbox.sourceware.org/gcc-bugs/
i get 404 for every link there.
ATM this renders to e.g.:
---8<---
[Bug fortran/66973] New: Incorrect resolution of generic interface with TYPE(C_PTR)
2023-04-12 18:48 UTC (2+ messages)
` [Bug fortran/66973] "
---8<---
source:
---8<---
<a
href="bug-66973-4@http.gcc.gnu.org%2Fbugzilla%2F/T/#t">[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-66973-4-10qXbFF8QB@http.gcc.gnu.org%2Fbugzilla%2F/T/#u">[Bug fortran/66973]</a> "
---8<---
The first link yields a 404
https://inbox.sourceware.org/gcc-bugs/bug-66973-4@http.gcc.gnu.org%2Fbugzilla%2F/T/#t
and the second link likewise returns 404
https://inbox.sourceware.org/gcc-bugs/bug-101018-4-9OS85Mwt0G@http.gcc.gnu.org%2Fbugzilla%2F/T/#u
Instead of the 404, i would have hoped to see the contents
of something like
https://gcc.gnu.org/pipermail/gcc-bugs/2023-April/818551.html
for the first link
and for the second (probably) gcc.gnu.org/PR66973#c7
Note that this 404 seems to happen to all bugzilla mails, e.g. in
https://inbox.sourceware.org/overseers/
there is "[Bug Infrastructure/29619] New: Setup gitolite for projects"
which points to
https://inbox.sourceware.org/overseers/bug-29619-14326@http.sourceware.org%2Fbugzilla%2F/T/#t
which also gives a 404.
PS: Currently we have an URL rewrite for gcc.gnu.org/ 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?
thanks!
next 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:
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=20230413120026.112fcfc1@nbbrfq \
--to=rep.dot.nop@gmail.com \
--cc=aldot@gcc.gnu.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).