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. 47b1f39c5e4a31073311c48a51872ccf7bd51659 Date: Sun, 30 May 2021 22:11:38 +0000 (GMT) [thread overview] Message-ID: <20210530221138.BADBE3858018@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 47b1f39c5e4a31073311c48a51872ccf7bd51659 (commit) from 0ff205ff678c35addd412a6e405edb034ad65b23 (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 47b1f39c5e4a31073311c48a51872ccf7bd51659 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Mon May 31 00:11:01 2021 +0200 wwwdocs: Nick's Blog has moved diff --git a/htdocs/index.html b/htdocs/index.html index 46969457..9f8392d9 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -138,7 +138,7 @@ mission statement</a>.</p> <div> <a href="https://gcc.gnu.org/news.html">Older news</a> | -<a href="https://developers.redhat.com/blog/author/nickclifton/">Nick's Blog</a> | +<a href="https://developers.redhat.com/author/nick-clifton">Nick's Blog</a> | <span class="smaller"> More news? Let gerald@pfeifer.com know! </span> ----------------------------------------------------------------------- Summary of changes: htdocs/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-05-30 22:11 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=20210530221138.BADBE3858018@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).