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. 821f00b7fa8b7369e6a8ccd12be675a838c304ab Date: Fri, 12 May 2023 19:57:23 +0000 (GMT) [thread overview] Message-ID: <20230512195723.438E7385840F@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 821f00b7fa8b7369e6a8ccd12be675a838c304ab (commit) from a5a3dc2f85786b038bc66b0e1929fdc67095397b (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 821f00b7fa8b7369e6a8ccd12be675a838c304ab Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Fri May 12 21:54:36 2023 +0200 gcc-13/buildstat: Remove trace of XHTML diff --git a/htdocs/gcc-13/buildstat.html b/htdocs/gcc-13/buildstat.html index fd6ee9e7..a54d0214 100644 --- a/htdocs/gcc-13/buildstat.html +++ b/htdocs/gcc-13/buildstat.html @@ -4,7 +4,7 @@ <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>Build status for GCC 13</title> -<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" /> +<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css"> </head> <body> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/buildstat.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-05-12 19:57 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=20230512195723.438E7385840F@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).