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. d472f751802f95635997649ea7ec71e4f725aa50
Date: Mon, 19 Feb 2024 20:44:28 +0000 (GMT)	[thread overview]
Message-ID: <20240219204428.3A5273858CDB@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  d472f751802f95635997649ea7ec71e4f725aa50 (commit)
      from  60dfe344b601a225cf477da1720517872175dd1a (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 d472f751802f95635997649ea7ec71e4f725aa50
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Feb 19 20:44:12 2024 +0000

    Fix "using using" typo

diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index 901a1653..35274691 100644
--- a/htdocs/gcc-14/porting_to.html
+++ b/htdocs/gcc-14/porting_to.html
@@ -146,7 +146,7 @@ standard C mode, which can result in implicit function declarations.
 To address this, the <code>-std=c11</code> option can be
 dropped, <code>-std=gnu11</code> can be used instead,
 or <code>-std=c11 -D_DEFAULT_SOURCE</code> can be used re-enable
-common extensions.  Alternatively, projects using using Autoconf
+common extensions.  Alternatively, projects using Autoconf
 could enable <code>AC_USE_SYSTEM_EXTENSIONS</code>.
 
 <p>

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-02-19 20:44 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=20240219204428.3A5273858CDB@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: 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).