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. b465e8f1f72a0718aebcf483a78b68c3e68ead72
Date: Fri,  2 Sep 2022 19:42:21 +0000 (GMT)	[thread overview]
Message-ID: <20220902194221.699E03858D1E@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  b465e8f1f72a0718aebcf483a78b68c3e68ead72 (commit)
      from  2761bb312d5feae8bff6fa503848380b965afb3b (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 b465e8f1f72a0718aebcf483a78b68c3e68ead72
Author: Thomas Schwinge <thomas@schwinge.name>
Date:   Fri Sep 2 21:39:18 2022 +0200

    GNU Tools Cauldron 2022

diff --git a/htdocs/index.html b/htdocs/index.html
index 3bec379e..c2982a74 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -55,6 +55,10 @@ mission statement</a>.</p>
 <h2 id="news">News</h2>
 <dl>
 
+<dt><span><a href="https://gcc.gnu.org/wiki/cauldron2022">GNU Tools Cauldron 2022</a></span>
+    <span class="date">[2022-09-02]</span></dt>
+    <dd>Prague, Czech Republic and online, September 16-18 2022</dd>
+
 <dt><span><a href="gcc-12/">GCC 12.2</a> released</span>
     <span class="date">[2022-08-19]</span></dt>
     <dd></dd>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/index.html | 4 ++++
 1 file changed, 4 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-09-02 19:42 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=20220902194221.699E03858D1E@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: 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).