public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. f71bc7f00c3a06c2645dd739471bd65c9c0586d9 Date: Mon, 30 Oct 2023 15:14:53 +0000 (GMT) [thread overview] Message-ID: <20231030151453.CD6653858C2F@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 f71bc7f00c3a06c2645dd739471bd65c9c0586d9 (commit) from f83141b2c816b09a2dd44ea5a84d868b7f0e50e7 (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 f71bc7f00c3a06c2645dd739471bd65c9c0586d9 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Oct 30 15:11:26 2023 +0000 Uncomment link to "Porting to GCC 14" diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 5611fc4f..e5d3970c 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -17,11 +17,9 @@ <p> This page is a "brief" summary of some of the huge number of improvements in GCC 14. -<!-- You may also want to check out our <a href="porting_to.html">Porting to GCC 14</a> page and the <a href="../onlinedocs/index.html#current">full GCC documentation</a>. ---> </p> <p>Note: GCC 14 has not been released yet, so this document is ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 2 -- 1 file changed, 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-10-30 15:14 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=20231030151453.CD6653858C2F@sourceware.org \ --to=redi@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).