public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: gerald@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 553b5e98de2dc90183773b0c0d750db62d6ad8db
Date: Fri, 29 Nov 2019 16:43:00 -0000 [thread overview]
Message-ID: <20191129164311.116792.qmail@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 553b5e98de2dc90183773b0c0d750db62d6ad8db (commit)
from 1b74d49d8fced10117e17f6509d16663bb43d61f (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 553b5e98de2dc90183773b0c0d750db62d6ad8db
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Fri Nov 29 17:40:34 2019 +0100
Make gcc-9/ and gcc-10/ a bit more uniform (wrt. <link rel="stylesheet">).
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index f0f0d31..5cca097 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -1,8 +1,10 @@
<!DOCTYPE html>
<html lang="en">
+
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>GCC 10 Release Series — Changes, New Features, and Fixes</title>
+<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" />
</head>
<!-- GCC maintainers, please do not hesitate to contribute/update
diff --git a/htdocs/gcc-10/criteria.html b/htdocs/gcc-10/criteria.html
index 3a50c74..b870b82 100644
--- a/htdocs/gcc-10/criteria.html
+++ b/htdocs/gcc-10/criteria.html
@@ -4,7 +4,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>GCC 10 Release Criteria</title>
-<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" /> </head>
+<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" />
+</head>
<body>
diff --git a/htdocs/gcc-9/changes.html b/htdocs/gcc-9/changes.html
index 9266139..c0e581f 100644
--- a/htdocs/gcc-9/changes.html
+++ b/htdocs/gcc-9/changes.html
@@ -1,5 +1,6 @@
<!DOCTYPE html>
<html lang="en">
+
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>GCC 9 Release Series — Changes, New Features, and Fixes</title>
diff --git a/htdocs/gcc-9/criteria.html b/htdocs/gcc-9/criteria.html
index 9c0fa1a..d434646 100644
--- a/htdocs/gcc-9/criteria.html
+++ b/htdocs/gcc-9/criteria.html
@@ -4,7 +4,8 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>GCC 9 Release Criteria</title>
-<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" /> </head>
+<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" />
+</head>
<body>
-----------------------------------------------------------------------
Summary of changes:
htdocs/gcc-10/changes.html | 2 ++
htdocs/gcc-10/criteria.html | 3 ++-
htdocs/gcc-9/changes.html | 1 +
htdocs/gcc-9/criteria.html | 3 ++-
4 files changed, 7 insertions(+), 2 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2019-11-29 16:43 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=20191129164311.116792.qmail@sourceware.org \
--to=gerald@gcc.gnu.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).