public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 7ef3b9f78e845e8e2b54ab485b35c707750065c6 Date: Tue, 30 Aug 2022 13:49:28 +0000 (GMT) [thread overview] Message-ID: <20220830134928.CE9563851C1A@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 7ef3b9f78e845e8e2b54ab485b35c707750065c6 (commit) from 2d804c95d2281cff93c037c3e0c79c83859d8bda (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 7ef3b9f78e845e8e2b54ab485b35c707750065c6 Author: Martin Liska <mliska@suse.cz> Date: Tue Aug 30 15:49:09 2022 +0200 m32c-rtems target was removed diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 058c2089..e73ac200 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -28,8 +28,8 @@ a work-in-progress.</p> <!-- .................................................................. --> <h2>Caveats</h2> <ul> - <li>The support for the <code>cr16-elf</code>, <code>tilegx*-linux</code> and <code>tilepro*-linux</code> - configurations has been removed.</li> + <li>The support for the <code>cr16-elf</code>, <code>tilegx*-linux</code>, <code>tilepro*-linux</code> + and <code>m32c-rtems</code> configurations has been removed.</li> </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-08-30 13:49 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=20220830134928.CE9563851C1A@sourceware.org \ --to=marxin@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).