Typo on GCC 14 porting_to page

Typo on GCC 14 porting_to page

[peter0x44]

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.

Re: Typo on GCC 14 porting_to page

[Jonathan Wakely]

[-- 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>