From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 2B23A385841A for ; Thu, 25 Aug 2022 12:54:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2B23A385841A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id C904C302AB2C; Thu, 25 Aug 2022 14:54:42 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 82BD8403B351; Thu, 25 Aug 2022 14:54:42 +0200 (CEST) Message-ID: <8e93a7e4cf4864304fa24febcdd5f4ebe113a31e.camel@klomp.org> Subject: Re: public-inbox for gcc lists From: Mark Wielaard To: Alexander Monakov Cc: gcc@gcc.gnu.org Date: Thu, 25 Aug 2022 14:54:42 +0200 In-Reply-To: <366638be-397c-d74f-ef8c-952566f85dd4@ispras.ru> References: <024bd7d3816c397f5d7a906446b3bfbde92363fe.camel@klomp.org> <366638be-397c-d74f-ef8c-952566f85dd4@ispras.ru> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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=20 > > https://inbox.sourceware.org/ >=20 > 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