From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout-p-103.mailbox.org (mout-p-103.mailbox.org [IPv6:2001:67c:2050:0:465::103]) by sourceware.org (Postfix) with ESMTPS id 16CF33858D32 for ; Mon, 23 Jan 2023 01:21:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 16CF33858D32 Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=aarsen.me Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=aarsen.me Received: from smtp102.mailbox.org (smtp102.mailbox.org [10.196.197.102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-103.mailbox.org (Postfix) with ESMTPS id 4P0XPh1bM1z9sPp; Mon, 23 Jan 2023 02:21:44 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aarsen.me; s=MBO0001; t=1674436904; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=vcsmB13B+WLdOLcPi3YSzUtbp+dyEhw/fKjt3CZnDWE=; b=I7P2qvXpkGKf4I7xutPeXjhkD90oqH7OQ49fR4QGnty8JWFDNH7QyVjwzEGZGftI4fkzV5 C0uK4m0fmuuFk3tzZI1PQW0Hr2sgs/H3ajoEUOf8eBrby/FWsRDOFlVy4Sfml4fW5QoJsF 7ESoLBg9tlA0RZARYzhRHvHqp/V4szIyezEJTKvJwvkjKSwJLN34El1G1dhoZ7UIuJjOGT +e4Gry8OMr9sKnHNlpsasr2a6NNRf9fJdmHM7PNmgGSwPOEgAawHFV3V/1X6S7bmk8aYMf /jdU1OlKy842O0M/71X3UFFGvr8Q+fMTl0BsQ/oaV2aOVab/TCor6nLAfgxlfA== From: =?UTF-8?q?Arsen=20Arsenovi=C4=87?= To: gcc-patches@gcc.gnu.org Cc: =?UTF-8?q?Arsen=20Arsenovi=C4=87?= Subject: [wwwdocs] lists: Add documentation about the Sourceware public-inbox Date: Mon, 23 Jan 2023 02:21:00 +0100 Message-Id: <20230123012100.4021860-1-arsen@aarsen.me> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-10.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,GIT_PATCH_0,KAM_INFOUSMEBIZ,KAM_SHORT,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --- Evening, I've gone through lists.html and documented the Sourceware public-inbox instance, since it seems to be commonly missed, yet some might find useful. This patch includes: - A brief summary of what the public-inbox provides, - A brief summary on alternative methods of accessing the archives, and - Convenience links next to each ML link that allows the reader to quickly jump to the public-inbox. Thanks in advance, have a lovely night! htdocs/lists.html | 110 ++++++++++++++++++++++++++++++++++++---------- 1 file changed, 88 insertions(+), 22 deletions(-) diff --git a/htdocs/lists.html b/htdocs/lists.html index b50e9ac3..89be66c9 100644 --- a/htdocs/lists.html +++ b/htdocs/lists.html @@ -21,11 +21,57 @@ Please make yourself familiar with our policies before subscribing and posting to these lists.

+

+ The mailing lists are available in two frontends: the traditional Pipermail + and the newer public-inbox, which + some might find more friendly or useful, as it allows following threads that + span months, etc. Both are linked below, with (inbox) leading + to the public-inbox archive. +

+ +

+ The public-inbox archives also provide an alternative search interface. It + is described on the help page for each index (as an example, see the + gcc-help help + page), in the search section. +

+ +

+ You might also be interested in accessing the archives via alternative + protocols. Two are supported: +

+ +
+
Git
+
+ The archives are indexed by git, and + hence, they can be downloaded in full or mirrored by anyone. The format + for the URLs of these repositories + is https://inbox.sourceware.org/listname/epoch. + Please consult each lists respective page for a list of available epochs, + as well as complete instructions. +
+
NNTP
+
Sourceware exposes read-only NNTP access + via nntp://inbox.sourceware.org/inbox.gcc.listname. + A similar scheme works for other projects indexed on + the public-inbox, but with + different prefixes. Please consult the mirror page of each list for more + information. +
+
IMAP
+
Similarly, archives are also exposed over IMAP via + imap://;AUTH=ANONYMOUS@inbox.sourceware.org/inbox.gcc.listname. + More information about IMPA access is also available on the respective + lists mirror page. +
+

Announcement lists:

@@ -33,11 +79,13 @@ before subscribing and posting to these lists.

Open lists:

    -
  • gcc-help +
  • gcc-help + (inbox) is a relatively high volume list for people searching for help in building or using GCC.
    • -

  • gcc +

  • gcc + (inbox) is a high volume list for general development discussions about GCC. Anything relevant to the development or testing of GCC and not covered by other mailing lists is suitable for discussion here.

    @@ -52,25 +100,30 @@ before subscribing and posting to these lists. sufficient to follow the major trends and important news in GCC's development process.

    • -
  • gcc-bugs +
  • gcc-bugs + (inbox) is a relatively high volume list with mails from our bug-tracking system.
    • -
  • gcc-patches +
  • gcc-patches + (inbox) is a relatively high volume list for patch submissions and discussion of particular patches. All patches (including those for front ends and web pages) and all discussion for a particular patch should be sent to this list.
    • -
  • - gcc-testresults is a moderate volume list where test results for +
  • gcc-testresults + (inbox) + is a moderate volume list where test results for the GCC compilers are posted.
    • -
  • gcc-regression +
  • gcc-regression + (inbox) is a moderate volume list where regression results for the GCC compilers are posted.
    • -
  • gcc-rust +
  • gcc-rust + (inbox) is for discussing Rust support in GCC. Patches should be sent to both this list and gcc-patches.
    • @@ -80,13 +133,15 @@ before subscribing and posting to these lists. library (libstdc++-v3). Patches to libstdc++-v3 should be sent to both this list and gcc-patches. -
  • fortran +
  • fortran + (inbox) is the main discussion and development list for the Fortran language front end of GCC, and the corresponding runtime library. Patches to gfortran and libgfortran should go to both this list and gcc-patches.
    • -
  • jit +
  • jit + (inbox) is for discussion and development of libgccjit, an experimental library for implementing Just-In-Time compilation using GCC as a back end. @@ -94,7 +149,8 @@ before subscribing and posting to these lists. Patches for the jit branch should go to both this list and gcc-patches.
    • -
  • gnutools-advocacy +
  • gnutools-advocacy + (inbox) is for discussion of marketing, promotion, recruiting and advocacy for the entire GNU Toolchain (Binutils, GAS, GCC, GDB, GLIBC, GLD, and Gold).
@@ -102,20 +158,24 @@ before subscribing and posting to these lists.

Read only lists:

    -
  • gcc-cvs +
  • gcc-cvs + (inbox) is a read-only, relatively high volume list which tracks checkins to the GCC source repository.
    • -
  • libstdc++-cvs +
  • libstdc++-cvs + (inbox) is a read-only, relatively low volume list which tracks checkins to the libstdc++-v3 part of the GCC repository. This is a subset of the messages to gcc-cvs.
    • -
  • gcc-cvs-wwwdocs +
  • gcc-cvs-wwwdocs + (inbox) is a read-only, relatively low volume list which tracks checkins to the GCC webpages repository.
    • -
  • gccadmin +
  • gccadmin + (inbox) is a read-only moderate volume list where output from cron jobs run by the gccadmin account on gcc.gnu.org is posted.
    • @@ -124,15 +184,18 @@ before subscribing and posting to these lists.

    Historical lists (archives only, no longer in use):

      -
    • gcc-prs +
    • gcc-prs + (inbox) was a read-only, relatively high volume list which tracked problem reports as they were entered into our database.
      • -
    • java +
    • java + (inbox) was the main discussion and development list for the Java language front end of GCC, and the corresponding runtime library.
      • -
    • java-announce +
    • java-announce + (inbox) was a low-volume, moderated, announcements-only list. Only announcements related to the Java language front end or runtime library were posted here.
      • @@ -142,17 +205,20 @@ before subscribing and posting to these lists. not archived. Messages sent here were also sent to gcc-cvs. -
    • java-patches +
    • java-patches + (inbox) was a list for submission and discussion of patches to libgcj, the Java runtime. Patches to GCJ, the Java language front end, should have gone to both this list and gcc-patches.
      • -
    • java-prs +
    • java-prs + (inbox) was a read-only list which tracked Java-related problem reports as they were entered into our database. Messages sent here were also sent to gcc-prs.
      • -
    • libstdc++-prs +
    • libstdc++-prs + (inbox) was formerly used by the libstdc++-v3 problem report database. libstdc++-v3 now uses the main GCC database and the gcc-bugs list.
    -- 2.39.1