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. 614d0c9e3c5139f8715a9100bb0aa55cf3b41700
Date: Tue, 17 Jan 2023 21:12:33 +0000 (GMT) [thread overview]
Message-ID: <20230117211233.CABBE3857400@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 614d0c9e3c5139f8715a9100bb0aa55cf3b41700 (commit)
from fc681f5412c421ff9609aea448310106d2570fd5 (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 614d0c9e3c5139f8715a9100bb0aa55cf3b41700
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Tue Jan 17 22:11:39 2023 +0100
rsync: Remove trailing slash from <meta> tags
diff --git a/htdocs/rsync.html b/htdocs/rsync.html
index e206f0b4..264ea2af 100644
--- a/htdocs/rsync.html
+++ b/htdocs/rsync.html
@@ -3,8 +3,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<meta name="description" content="Anonymous rsync read-only access to the GCC project." />
-<meta name="keywords" content="version control, GCC, source, public, repository, rsync" />
+<meta name="description" content="Anonymous rsync read-only access to the GCC project.">
+<meta name="keywords" content="version control, GCC, source, public, repository, rsync">
<title>GCC: Anonymous read-only rsync access</title>
<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
</head>
-----------------------------------------------------------------------
Summary of changes:
htdocs/rsync.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2023-01-17 21:12 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=20230117211233.CABBE3857400@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).