public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. f492e1d651aba79760a384c04941b699eb9d811e Date: Thu, 16 Sep 2021 07:27:30 +0000 (GMT) [thread overview] Message-ID: <20210916072730.AF8DC3858D3C@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 f492e1d651aba79760a384c04941b699eb9d811e (commit) via 51e2e792d8a66436df126a28e870ac9f38767600 (commit) from f4e66a329096bb1f9f0fc51bd8a5b35cad77f1b8 (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 f492e1d651aba79760a384c04941b699eb9d811e Author: Thomas Schwinge <thomas@codesourcery.com> Date: Thu Sep 16 09:25:06 2021 +0200 Simplify 'held through online videoconference' to 'held online' diff --git a/htdocs/index.html b/htdocs/index.html index c7368e26..00df1d46 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -57,7 +57,7 @@ mission statement</a>.</p> <dt><span><a href="https://gcc.gnu.org/wiki/linuxplumbers2021">GNU Tools @ Linux Plumbers Conference 2021</a></span> <span class="date">[2021-09-15]</span></dt> - <dd>Will be held through online videoconference, September 20-24 2021</dd> + <dd>Will be held online, September 20-24 2021</dd> <dt><span><a href="gcc-11/">GCC 11.2</a> released</span> <span class="date">[2021-07-28]</span></dt> @@ -85,7 +85,7 @@ mission statement</a>.</p> <dt><span><a href="https://gcc.gnu.org/wiki/linuxplumbers2020">GNU Tools @ Linux Plumbers Conference 2020</a></span> <span class="date">[2020-07-17]</span></dt> - <dd>Will be held through online videoconference, August 24-28 2020</dd> + <dd>Will be held online, August 24-28 2020</dd> <dt><span><a href="gcc-10/">GCC 10.1</a> released</span> <span class="date">[2020-05-07]</span></dt> commit 51e2e792d8a66436df126a28e870ac9f38767600 Author: Thomas Schwinge <thomas@codesourcery.com> Date: Wed Sep 15 17:08:12 2021 +0200 GNU Tools @ Linux Plumbers Conference 2021 diff --git a/htdocs/index.html b/htdocs/index.html index d6b0d959..c7368e26 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -54,6 +54,11 @@ mission statement</a>.</p> <td class="news border0"> <h2 id="news">News</h2> <dl> + +<dt><span><a href="https://gcc.gnu.org/wiki/linuxplumbers2021">GNU Tools @ Linux Plumbers Conference 2021</a></span> + <span class="date">[2021-09-15]</span></dt> + <dd>Will be held through online videoconference, September 20-24 2021</dd> + <dt><span><a href="gcc-11/">GCC 11.2</a> released</span> <span class="date">[2021-07-28]</span></dt> <dd></dd> ----------------------------------------------------------------------- Summary of changes: htdocs/index.html | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-09-16 7:27 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=20210916072730.AF8DC3858D3C@sourceware.org \ --to=tschwinge@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).