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. c82e0f875b6bc733e59fb144f76119f8000619cf
Date: Thu,  3 Jun 2021 11:27:38 +0000 (GMT)	[thread overview]
Message-ID: <20210603112738.89F08383F423@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  c82e0f875b6bc733e59fb144f76119f8000619cf (commit)
      from  95cf0688ab3b1973f60133d32bcd29e373186cec (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 c82e0f875b6bc733e59fb144f76119f8000619cf
Author: Martin Liska <mliska@suse.cz>
Date:   Thu Jun 3 13:27:31 2021 +0200

    Add id for a header.

diff --git a/htdocs/lists.html b/htdocs/lists.html
index e9636198..ef3e7a73 100644
--- a/htdocs/lists.html
+++ b/htdocs/lists.html
@@ -214,7 +214,7 @@ who has said "I can't get off this list!  Unsubscribe me!" has found,
 with enough prodding, that sending mail to the address listed in
 <code>List-Unsubscribe:</code> does the trick.</p>
 
-<h2>Filtering</h2>
+<h2 id="filtering">Filtering</h2>
 
 <p>If you want to use procmail or similar tools to process the GCC
 mailing lists, you can filter using the List-Id: header from RFC2919, as well

-----------------------------------------------------------------------

Summary of changes:
 htdocs/lists.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-06-03 11:27 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=20210603112738.89F08383F423@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: 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).