public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: gcc@gcc.gnu.org
Subject: Re: public-inbox for gcc lists
Date: Thu, 25 Aug 2022 14:54:42 +0200	[thread overview]
Message-ID: <8e93a7e4cf4864304fa24febcdd5f4ebe113a31e.camel@klomp.org> (raw)
In-Reply-To: <366638be-397c-d74f-ef8c-952566f85dd4@ispras.ru>

Hi Alexander,

On Thu, 2022-08-25 at 15:45 +0300, Alexander Monakov wrote:
> On Thu, 25 Aug 2022, Mark Wielaard wrote:
> > Given that gcc is part of the sourceware family the mailinglists
> > are now also available through the public-inbox instance at 
> > https://inbox.sourceware.org/
> 
> Thanks for this. At the moment something seems broken with a few
> lists,
> as clicking on a thread results in a 404 page, e.g. any top link from
> https://inbox.sourceware.org/gcc-bugs/

Yes, sadly that is one of the known issues with bugzilla emails:

> - Message-IDs can contain slashes ('/') which are sometimes
>   encoded as %2F. If you got an URL with "%2F" in the path change
>   it to an actual '/' character to workaround it
>   (which doesn't work if the Message-ID ends with a / which is
>    the case for bugzilla generated emails).
>   We are looking to see if we can get the slash handling more
>   consistent.

For now please use bugzilla to search through bugs.

Apologies for the brokenness. Hope other lists are more useful.

Cheers,

Mark

      reply	other threads:[~2022-08-25 12:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 11:44 Mark Wielaard
2022-08-25 12:45 ` Alexander Monakov
2022-08-25 12:54   ` Mark Wielaard [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=8e93a7e4cf4864304fa24febcdd5f4ebe113a31e.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=amonakov@ispras.ru \
    --cc=gcc@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).