public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 94e51dd51b4cc699592cc40bf78687920a9a2f4a Date: Mon, 15 Jun 2020 09:21:55 +0000 (GMT) [thread overview] Message-ID: <20200615092155.A7CC33851C20@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 94e51dd51b4cc699592cc40bf78687920a9a2f4a (commit) from 8be05148b4190ad49ceefb9bac0a75113c1aaa55 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 94e51dd51b4cc699592cc40bf78687920a9a2f4a Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Jun 15 10:20:58 2020 +0100 Use past tense for descriptions of historical mailing lists diff --git a/htdocs/lists.html b/htdocs/lists.html index ea37aedc..df45edd7 100644 --- a/htdocs/lists.html +++ b/htdocs/lists.html @@ -120,8 +120,8 @@ before <a href="#subscribe">subscribing</a> and posting to these lists. <ul> <li><b><a href="https://gcc.gnu.org/ml/gcc-prs/">gcc-prs</a></b> - was a read-only, relatively high volume list which tracks problem reports - as they are entered into our database.</li> + 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> was the main discussion and development list for the Java language @@ -129,27 +129,27 @@ before <a href="#subscribe">subscribing</a> and posting to these lists. <li><b><a href="https://gcc.gnu.org/ml/java-announce/">java-announce</a></b> was a low-volume, moderated, announcements-only list. Only announcements - related to the Java language front end or runtime library are posted + related to the Java language front end or runtime library were posted here.</li> <li><b>java-cvs</b> - tracked checkins to the Java language compiler and runtime. It is - not archived. Messages sent here are also sent to + tracked checkins to the Java language compiler and runtime. It was + 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> was a list for submission and discussion of patches to libgcj, the - Java runtime. Patches to GCJ, the Java language front end, should - go to both this list and <b>gcc-patches</b>.</li> + 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> - was a read-only list which tracks Java-related problem reports as - they are entered into our database. Messages sent here are + 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> was formerly used by the libstdc++-v3 problem report database. - libstdc++-v3 now uses the main GCC database and the <b>gcc-prs</b> list.</li> + libstdc++-v3 now uses the main GCC database and the <b>gcc-bugs</b> list.</li> </ul> <p>To post a message, just send mail to <i>listname</i><code>@gcc.gnu.org</code>.</p> ----------------------------------------------------------------------- Summary of changes: htdocs/lists.html | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-06-15 9:21 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200615092155.A7CC33851C20@sourceware.org \ --to=redi@sourceware.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).