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. 0b5bf5ae190bcf614b25bc85bc707aa29d3f879e Date: Mon, 16 Jan 2023 18:58:54 +0000 (GMT) [thread overview] Message-ID: <20230116185854.06D2E3858D33@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 0b5bf5ae190bcf614b25bc85bc707aa29d3f879e (commit) from 798323ccc7dbeb3e5df3653c16d0cbe40919c1d5 (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 0b5bf5ae190bcf614b25bc85bc707aa29d3f879e Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Mon Jan 16 19:57:50 2023 +0100 git: Remove trailing slash from <meta> tags diff --git a/htdocs/git.html b/htdocs/git.html index 4a8b1004..fc30c5ab 100644 --- a/htdocs/git.html +++ b/htdocs/git.html @@ -3,8 +3,8 @@ <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> -<meta name="description" content="Anonymous read-only access to the GCC project Git source repository." /> -<meta name="keywords" content="Git, version control, GCC, source, public, repository" /> +<meta name="description" content="Anonymous read-only access to the GCC project Git source repository."> +<meta name="keywords" content="Git, version control, GCC, source, public, repository"> <title>GCC: Anonymous read-only Git access</title> <link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css"> </head> ----------------------------------------------------------------------- Summary of changes: htdocs/git.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-01-16 18:58 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=20230116185854.06D2E3858D33@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: 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).