From: "Arsen Arsenović" <arsen@aarsen.me>
To: gcc-patches@gcc.gnu.org
Cc: "Arsen Arsenović" <arsen@aarsen.me>
Subject: Re: [wwwdocs] lists: Add documentation about the Sourceware public-inbox
Date: Mon, 23 Jan 2023 02:24:05 +0100 [thread overview]
Message-ID: <865ycyjb4m.fsf@aarsen.me> (raw)
In-Reply-To: <20230123012100.4021860-1-arsen@aarsen.me>
[-- Attachment #1: Type: text/plain, Size: 12665 bytes --]
Arsen Arsenović <arsen@aarsen.me> writes:
> ---
> 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 <a href="#policies">our policies</a>
> before <a href="#subscribe">subscribing</a> and posting to these lists.
> </p>
>
> +<p>
> + The mailing lists are available in two frontends: the traditional Pipermail
> + and the newer <a href="https://public-inbox.org/">public-inbox</a>, which
> + some might find more friendly or useful, as it allows following threads that
> + span months, etc. Both are linked below, with <code>(inbox)</code> leading
> + to the public-inbox archive.
> +</p>
> +
> +<p>
> + 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
> + <a href="https://inbox.sourceware.org/gcc-help/_/text/help/">gcc-help help
> + page</a>), in the <code>search</code> section.
> +</p>
> +
> +<p>
> + You might also be interested in accessing the archives via alternative
> + protocols. Two are supported:
> +</p>
Gah! This should say three, of course. I didn't notice before sending.
Please amend if applying.
> +<dl>
> + <dt>Git</dt>
> + <dd>
> + The archives are indexed by <a href="https://git-scm.com/">git</a>, and
> + hence, they can be downloaded in full or mirrored by anyone. The format
> + for the URLs of these repositories
> + is <code>https://inbox.sourceware.org/<i>listname</i>/<i>epoch</i></code>.
> + Please consult each lists respective page for a list of available epochs,
> + as well as complete instructions.
> + </dd>
> + <dt>NNTP</dt>
> + <dd>Sourceware exposes read-only NNTP access
> + via <code>nntp://inbox.sourceware.org/inbox.gcc.<i>listname</i></code>.
> + A similar scheme works for other projects indexed on
> + the <a href="https://inbox.sourceware.org/">public-inbox</a>, but with
> + different prefixes. Please consult the mirror page of each list for more
> + information.
> + </dd>
> + <dt>IMAP</dt>
> + <dd>Similarly, archives are also exposed over IMAP via
> + <code>imap://;AUTH=ANONYMOUS@inbox.sourceware.org/inbox.gcc.<i>listname</i></code>.
> + More information about IMPA access is also available on the respective
> + lists mirror page.
> + </dd>
> +</dl>
>
> <p>Announcement lists:</p>
>
> <ul>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-announce/">gcc-announce</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-announce/">gcc-announce</a>
> + <a href="https://inbox.sourceware.org/gcc-announce">(inbox)</a></b>
> is a read-only low volume list where
> we post announcements about releases or other important events.</li>
> </ul>
> @@ -33,11 +79,13 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
> <p>Open lists:</p>
>
> <ul>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-help/">gcc-help</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-help/">gcc-help</a>
> + <a href="https://inbox.sourceware.org/gcc-help">(inbox)</a></b>
> is a relatively high volume list for people searching for help in
> building or using GCC.</li>
>
> - <li><p><b><a href="https://gcc.gnu.org/ml/gcc/">gcc</a></b>
> + <li><p><b><a href="https://gcc.gnu.org/ml/gcc/">gcc</a>
> + <a href="https://inbox.sourceware.org/gcc">(inbox)</a></b>
> 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.</p>
> @@ -52,25 +100,30 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
> sufficient to follow the major trends and important news in GCC's
> development process.</p></li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-bugs/">gcc-bugs</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-bugs/">gcc-bugs</a>
> + <a href="https://inbox.sourceware.org/gcc-bugs">(inbox)</a></b>
> is a relatively high volume list with mails from our
> bug-tracking system.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-patches/">gcc-patches</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-patches/">gcc-patches</a>
> + <a href="https://inbox.sourceware.org/gcc-patches">(inbox)</a></b>
> 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.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-testresults/">
> - gcc-testresults</a></b> is a moderate volume list where test results for
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults</a>
> + <a href="https://inbox.sourceware.org/gcc-testresults">(inbox)</a></b>
> + is a moderate volume list where test results for
> the GCC compilers are posted.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-regression/">gcc-regression</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-regression/">gcc-regression</a>
> + <a href="https://inbox.sourceware.org/gcc-regression">(inbox)</a></b>
> is a moderate volume list where regression results for the GCC compilers
> are posted.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-rust/">gcc-rust</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-rust/">gcc-rust</a>
> + <a href="https://inbox.sourceware.org/gcc-rust">(inbox)</a></b>
> is for discussing <a href="https://gcc.gnu.org/wiki/RustFrontEnd">Rust
> support in GCC</a>.
> Patches should be sent to both this list and <b>gcc-patches</b>.</li>
> @@ -80,13 +133,15 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
> library (libstdc++-v3). Patches to libstdc++-v3 should be sent to
> both this list and <b>gcc-patches</b>.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/fortran/">fortran</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/fortran/">fortran</a>
> + <a href="https://inbox.sourceware.org/fortran">(inbox)</a></b>
> 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
> <b>gcc-patches</b>.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/jit/">jit</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/jit/">jit</a>
> + <a href="https://inbox.sourceware.org/jit">(inbox)</a></b>
> is for discussion and development of
> <a href="https://gcc.gnu.org/wiki/JIT">libgccjit</a>, an experimental
> library for implementing Just-In-Time compilation using GCC as a back end.
> @@ -94,7 +149,8 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
> Patches for the jit branch should go to both this list and
> <b>gcc-patches</b>.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/gnutools-advocacy/">gnutools-advocacy</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gnutools-advocacy/">gnutools-advocacy</a>
> + <a href="https://inbox.sourceware.org/gnutools-advocacy">(inbox)</a></b>
> is for discussion of marketing, promotion, recruiting and advocacy for
> the entire GNU Toolchain (Binutils, GAS, GCC, GDB, GLIBC, GLD, and Gold).</li>
> </ul>
> @@ -102,20 +158,24 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
> <p>Read only lists:</p>
>
> <ul>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-cvs/">gcc-cvs</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-cvs/">gcc-cvs</a>
> + <a href="https://inbox.sourceware.org/gcc-cvs">(inbox)</a></b>
> is a read-only, relatively high volume list which tracks checkins to the
> GCC source repository.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/libstdc++-cvs/">libstdc++-cvs</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/libstdc++-cvs/">libstdc++-cvs</a>
> + <a href="https://inbox.sourceware.org/libstdc++-cvs">(inbox)</a></b>
> 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 <b>gcc-cvs</b>.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-cvs-wwwdocs/">gcc-cvs-wwwdocs</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-cvs-wwwdocs/">gcc-cvs-wwwdocs</a>
> + <a href="https://inbox.sourceware.org/gcc-cvs-wwwdocs">(inbox)</a></b>
> is a read-only, relatively low volume list which tracks checkins to
> the GCC webpages repository.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/gccadmin/">gccadmin</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gccadmin/">gccadmin</a>
> + <a href="https://inbox.sourceware.org/gccadmin">(inbox)</a></b>
> is a read-only moderate volume list where output from
> <code>cron</code> jobs run by the <code>gccadmin</code> account on
> gcc.gnu.org is posted.</li>
> @@ -124,15 +184,18 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
> <p>Historical lists (archives only, no longer in use):</p>
>
> <ul>
> - <li><b><a href="https://gcc.gnu.org/ml/gcc-prs/">gcc-prs</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/gcc-prs/">gcc-prs</a>
> + <a href="https://inbox.sourceware.org/gcc-prs">(inbox)</a></b>
> was a read-only, relatively high volume list which tracked problem reports
> as they were entered into our database.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/java/">java</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/java/">java</a>
> + <a href="https://inbox.sourceware.org/java">(inbox)</a></b>
> was the main discussion and development list for the Java language
> front end of GCC, and the corresponding runtime library.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/java-announce/">java-announce</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/java-announce/">java-announce</a>
> + <a href="https://inbox.sourceware.org/java-announce">(inbox)</a></b>
> was a low-volume, moderated, announcements-only list. Only announcements
> related to the Java language front end or runtime library were posted
> here.</li>
> @@ -142,17 +205,20 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
> not archived. Messages sent here were also sent to
> <b>gcc-cvs</b>.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/java-patches/">java-patches</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/java-patches/">java-patches</a>
> + <a href="https://inbox.sourceware.org/java-patches">(inbox)</a></b>
> 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 <b>gcc-patches</b>.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/java-prs/">java-prs</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/java-prs/">java-prs</a>
> + <a href="https://inbox.sourceware.org/java-prs">(inbox)</a></b>
> 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 <b>gcc-prs</b>.</li>
>
> - <li><b><a href="https://gcc.gnu.org/ml/libstdc++-prs/">libstdc++-prs</a></b>
> + <li><b><a href="https://gcc.gnu.org/ml/libstdc++-prs/">libstdc++-prs</a>
> + <a href="https://inbox.sourceware.org/libstdc++-prs">(inbox)</a></b>
> was formerly used by the libstdc++-v3 problem report database.
> libstdc++-v3 now uses the main GCC database and the <b>gcc-bugs</b> list.</li>
> </ul>
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2023-01-23 1:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 1:21 Arsen Arsenović
2023-01-23 1:24 ` Arsen Arsenović [this message]
2023-02-13 21:41 ` Ping: " Arsen Arsenović
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=865ycyjb4m.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=gcc-patches@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).