public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 3d248f971092a43effc4b44e3cf9113bac6f4a5a
Date: Tue,  1 Nov 2022 09:46:28 +0000 (GMT)	[thread overview]
Message-ID: <20221101094628.BA14E3858D35@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  3d248f971092a43effc4b44e3cf9113bac6f4a5a (commit)
      from  6f0743aeca7a1a18089229a0defd23cf44d3e453 (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 3d248f971092a43effc4b44e3cf9113bac6f4a5a
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Tue Nov 1 10:46:07 2022 +0100

    readings: Remove <meta name="keywords">
    
    Google has not been using that forever and there are indications
    search engines even use it as one indication for spam sites.

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 01ccd55d..5622bcc3 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -8,7 +8,6 @@
 
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<meta name="keywords" content="GCC, compilers, optimization, documentation, FAQ, standards" />
 <title>Links and Selected Readings</title>
 <link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
 </head>

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

Summary of changes:
 htdocs/readings.html | 1 -
 1 file changed, 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-11-01  9:46 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=20221101094628.BA14E3858D35@sourceware.org \
    --to=gerald@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).