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 D08833858D28 for ; Thu, 25 Aug 2022 11:44:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D08833858D28 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 BF93F302AB2C for ; Thu, 25 Aug 2022 13:44:56 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 10A98403B351; Thu, 25 Aug 2022 13:44:56 +0200 (CEST) Message-ID: <024bd7d3816c397f5d7a906446b3bfbde92363fe.camel@klomp.org> Subject: public-inbox for gcc lists From: Mark Wielaard To: gcc@gcc.gnu.org Date: Thu, 25 Aug 2022 13:44:55 +0200 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,KAM_SHORT,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 gcc-hackers, 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/ In particular: https://inbox.sourceware.org/fortran https://inbox.sourceware.org/gcc https://inbox.sourceware.org/gcc-announce https://inbox.sourceware.org/gcc-help https://inbox.sourceware.org/gcc-patches https://inbox.sourceware.org/gcc-rust https://inbox.sourceware.org/jit https://inbox.sourceware.org/libstdc++ There are also archives of some older not used anymore lists in case people are interested in some history (we are aware that some of these older lists contain spam, we will try to remove that). And some of the automated lists like testresults, prs, cvs, etc. (but without full text search, please use bugzilla, git or bunsen for that). Note that you can now mirror these mailinglists through git (see the mirror instructions on each list), there is an atom link to follow the lists, you can download mboxes of search results and there are read- only nntp news and imap archives of each list (in the inbox.gcc.* hierarchy). To handle patches you might want to look at b4 or piem for emacs: https://git.kernel.org/pub/scm/utils/b4/b4.git https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/man/b4.5.rst https://git.kyleam.com/piem https://docs.kyleam.com/piem.html You will want the following in your .git/config: [b4] midmask =3D https://inbox.sourceware.org/gcc-patches/%s linkmask =3D https://inbox.sourceware.org.org/gcc-patches/%s There are currently some known issues: - 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. - HTML emails aren't accepted. Even if the list would strip the text/html part. Please don't sent HTML email. We are looking at stripping the HTML part and only importing the text/plain part into public-inbox. - Messages send to gcc-patches are sometimes not fully indexed, which means they won't show up when doing a full text search, but they are functional in all other ways that matter. We'll reindex the list periodically and look into why this is happening (gcc-patches is the largest list we have and we might just hit some limit). Your friendly sourceware overseers team (with special thanks to Simon Marchi for showing how to setup public-inbox and to Frank Eigler for making sure the sourceware infrastructure was ready). P.S.=20 inbox.sourceware.org is one part of the Sourceware GNU Toolchain Infrastructure roadmap to make email/git based workflow more fun, secure and productive by automating contribution tracking and testing across different distros and architectures: https://inbox.sourceware.org/overseers/YrLdfDWzq1T4k5xg@wildebeest.org/ There will be a Sourceware GNU Toolchain Infrastructure and beyond BoF at the Cauldron next month for everybody who likes to discuss (and wants to help with) automating the infrastructure to make contributing to our projects more fun and more productive: https://gcc.gnu.org/wiki/cauldron2022#cauldron2022talks.sourceware_gnu_tool= chain_infrastructure_and_beyond