public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 3733fbc6c15211ee367d0329cb2f57f29bfb1e83 Date: Thu, 3 Jun 2021 11:31:17 +0000 (GMT) [thread overview] Message-ID: <20210603113117.32303386FC1B@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 3733fbc6c15211ee367d0329cb2f57f29bfb1e83 (commit) from c82e0f875b6bc733e59fb144f76119f8000619cf (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 3733fbc6c15211ee367d0329cb2f57f29bfb1e83 Author: Martin Liska <mliska@suse.cz> Date: Thu Jun 3 13:31:09 2021 +0200 Fix validation error. diff --git a/htdocs/lists.html b/htdocs/lists.html index ef3e7a73..ad36a7e2 100644 --- a/htdocs/lists.html +++ b/htdocs/lists.html @@ -226,7 +226,7 @@ our lists into a single folder named INLIST.gcc:</p> <blockquote><p><code> :0<br /> -* ^List-Id: .*<.*.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 /> -* ^List-Id: .*<.*.gcc.gnu.org>$<br /> +* ^List-Id: .*<.*.gcc.gnu.org>$<br /> | formail -D 8192 msgid.cache </code></p></blockquote> ----------------------------------------------------------------------- Summary of changes: htdocs/lists.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-06-03 11:31 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=20210603113117.32303386FC1B@sourceware.org \ --to=marxin@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).