public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Segher Boessenkool <segher@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 8beab8102fd97e0bc745a285e619c08c52d74b6f Date: Tue, 1 Jun 2021 16:00:01 +0000 (GMT) [thread overview] Message-ID: <20210601160001.050163855008@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 8beab8102fd97e0bc745a285e619c08c52d74b6f (commit) from bbe2a2b6befc0cc919962920054cdf91849fd893 (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 8beab8102fd97e0bc745a285e619c08c52d74b6f Author: Segher Boessenkool <segher@kernel.crashing.org> Date: Tue Jun 1 15:50:57 2021 +0000 lists: Correct procmail recipe We haven't had Sender: for a while now. Use the standard List-Id: header in its place. diff --git a/htdocs/lists.html b/htdocs/lists.html index 42a44ab8..4ac5d5a8 100644 --- a/htdocs/lists.html +++ b/htdocs/lists.html @@ -217,8 +217,8 @@ with enough prodding, that sending mail to the address listed in <h2>Filtering</h2> <p>If you want to use procmail or similar tools to process the GCC -mailing lists, you can filter using the Sender: header, as well as all -of the RFC2369 headers (List-Subscribe, List-Unsubscribe, List-Post, +mailing lists, you can filter using the List-Id: header from RFC2919, as well +as all of the RFC2369 headers (List-Subscribe, List-Unsubscribe, List-Post, List-Archive, etc.).</p> <p>For example, the following procmail rule will sort all mail from @@ -226,7 +226,7 @@ our lists into a single folder named INLIST.gcc:</p> <blockquote><p><code> :0<br /> -* ^Sender: .*-owner@gcc.gnu.org<br /> +* ^List-Id: .*<.*@gcc.gnu.org>$<br /> INLIST.gcc<br /> </code></p></blockquote> @@ -235,7 +235,7 @@ can use the following recipe (Use at your own risk!):</p> <blockquote><p><code> :0 Wh: msgid.lock<br /> -* ^Sender: .*-owner@gcc.gnu.org<br /> +* ^List-Id: .*<.*@gcc.gnu.org>$<br /> | formail -D 8192 msgid.cache </code></p></blockquote> ----------------------------------------------------------------------- Summary of changes: htdocs/lists.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-06-01 16:00 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=20210601160001.050163855008@sourceware.org \ --to=segher@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).