public inbox for
help / color / mirror / Atom feed
From: Segher Boessenkool <>
Subject: gcc-wwwdocs branch master updated. 890401b1dfb48c33723980b7a0b30419315ff8ab
Date: Tue,  1 Jun 2021 21:47:18 +0000 (GMT)	[thread overview]
Message-ID: <> (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  890401b1dfb48c33723980b7a0b30419315ff8ab (commit)
      from  8beab8102fd97e0bc745a285e619c08c52d74b6f (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 890401b1dfb48c33723980b7a0b30419315ff8ab
Author: Segher Boessenkool <>
Date:   Tue Jun 1 21:42:12 2021 +0000

    lists: Fix thinko
    Brown paper bag time.  The List-Id: should look like a hostname, not
    like an email address.  Somehow I put in an at-sign when changing my
    gcc-patches example to the match-all example we have here.
    Note that the "." in the procmail match are RE wildcards btw.  This is
    common practice in procmailrcs, although not necessarily a good idea :-)

diff --git a/htdocs/lists.html b/htdocs/lists.html
index 4ac5d5a8..e9636198 100644
--- a/htdocs/lists.html
+++ b/htdocs/lists.html
@@ -226,7 +226,7 @@ our lists into a single folder named INLIST.gcc:</p>
 :0<br />
-* ^List-Id: .*<.*>$<br />
+* ^List-Id: .*<.*>$<br />
 INLIST.gcc<br />
@@ -235,7 +235,7 @@ can use the following recipe (Use at your own risk!):</p>
 :0 Wh: msgid.lock<br />
-* ^List-Id: .*<.*>$<br />
+* ^List-Id: .*<.*>$<br />
 | formail -D 8192 msgid.cache


Summary of changes:
 htdocs/lists.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


                 reply	other threads:[~2021-06-01 21:47 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).