public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jemarch@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. e848ac5c5df1c9446bcc8b314c279396533bf0fa
Date: Thu, 12 Jan 2023 14:07:37 +0000 (GMT)	[thread overview]
Message-ID: <20230112140737.90E183858C31@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  e848ac5c5df1c9446bcc8b314c279396533bf0fa (commit)
      from  4054e75517700a18a30520a02045ac01a69def4e (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 e848ac5c5df1c9446bcc8b314c279396533bf0fa
Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Date:   Thu Jan 12 15:11:31 2023 +0100

    Use a GCC BPF related example in the godbolt.org link
    
    * htdocs/index.html (News):

diff --git a/htdocs/index.html b/htdocs/index.html
index 192db418..08037653 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -55,7 +55,7 @@ mission statement</a>.</p>
 <h2 id="news">News</h2>
 <dl>
 
-<dt><span><a href="https://godbolt.org">GCC BPF in Compiler Explorer</a></span>
+<dt><span><a href="https://godbolt.org/z/GT1vGdzMb">GCC BPF in Compiler Explorer</a></span>
      <span class="date">[2022-12-23]</span></dt>
 <dd>Support for a nightly build of the bpf-unknown-none-gcc compiler
   has been contributed to Compiler Explorer (aka godbolt.org) by Marc

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

Summary of changes:
 htdocs/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-01-12 14:07 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=20230112140737.90E183858C31@sourceware.org \
    --to=jemarch@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).