From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: peter0x44 <peter0x44@disroot.org>
Cc: Gcc <gcc@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Typo on GCC 14 porting_to page
Date: Mon, 19 Feb 2024 20:45:18 +0000 [thread overview]
Message-ID: <CAH6eHdSpq36J9si5JnEANcKjUAZuGi2MjmJkOXfXM_toWk6MnA@mail.gmail.com> (raw)
In-Reply-To: <299f1e6f0ce0c69117f71f5a78b69895@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
On Mon, 19 Feb 2024 at 20:24, peter0x44 wrote:
>
> I was reading the GCC 14 porting to page and I noticed:
>
> Alternatively, projects using using Autoconf could enable
> AC_USE_SYSTEM_EXTENSIONS.
>
> "using using" should be "using".
>
> I read over the rest and didn't notice anything else wrong.
>
> Thanks,
> Peter D.
Thanks. I've fixed it with the attached patch, pushed to wwwdocs.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 794 bytes --]
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>
prev parent reply other threads:[~2024-02-19 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 20:23 peter0x44
2024-02-19 20:45 ` Jonathan Wakely [this message]
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=CAH6eHdSpq36J9si5JnEANcKjUAZuGi2MjmJkOXfXM_toWk6MnA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=peter0x44@disroot.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).