public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 1ffb91a0903b3c9e9157e0c0f7ab741fbaa321c9 Date: Thu, 23 Feb 2023 14:47:22 +0000 (GMT) [thread overview] Message-ID: <20230223144722.8D1043858C5E@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 1ffb91a0903b3c9e9157e0c0f7ab741fbaa321c9 (commit) from 324b81b41b986d0b77752209b6e3767d708893ad (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 1ffb91a0903b3c9e9157e0c0f7ab741fbaa321c9 Author: Tobias Burnus <tobias@codesourcery.com> Date: Thu Feb 23 15:46:41 2023 +0100 projects/gomp/index.html: Remove stray </code> diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html index 3ef4f502..fa770855 100644 --- a/htdocs/projects/gomp/index.html +++ b/htdocs/projects/gomp/index.html @@ -432,7 +432,7 @@ than listed, depending on resolved corner cases and optimizations.</p> </td> <td> Reverse offload unsupported<br> - Reverse offload supported</code> + Reverse offload supported </td> </tr> <tr> ----------------------------------------------------------------------- Summary of changes: htdocs/projects/gomp/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-02-23 14:47 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=20230223144722.8D1043858C5E@sourceware.org \ --to=burnus@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).