[DOCS] Mention removed ports in GCC 13.

  Ready for master?

Thanks,
Martin

---
 htdocs/gcc-13/changes.html | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
  

On Fri, Aug 26, 2022 at 8:33 AM Martin Liška <mliska@suse.cz> wrote:
>
> Ready for master?

OK

> Thanks,
> Martin
>
> ---
>  htdocs/gcc-13/changes.html | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> index c58ca1d4..e3f2ee44 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -28,7 +28,9 @@ a work-in-progress.</p>
>  <!-- .................................................................. -->
>  <h2>Caveats</h2>
>  <ul>
> -  <li>...</li>
> +    <li>The support for the <code>cr16-elf</code>, <code>tilegx*-linux</code> and <code>tilepro*-linux</code>
> +      configurations has been removed.</li>
> +</li>
>  </ul>
>
>
> --
> 2.37.2
>
  

On Fri, 26 Aug 2022, Martin Liška wrote:
> Ready for master?

Looks fine. Tthank you, Martin!

Gerald
  

On Fri, 26 Aug 2022, Richard Biener via Gcc-patches wrote:
>> Ready for master?
> OK

Actually both Richi and me missed a little detail:

>> -  <li>...</li>
>> +    <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 patch added one <li> plus two </li>s - fixed thusly.

Gerald


commit 0d66c0f73e9c54536070346bd4d52f61132ba012
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Mon Sep 5 20:28:57 2022 +0800

    gcc-13: Remove extraneous </li> under Caveats
    
    This snuck in via 79ecba7b which added two </li>s instead of one.

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 3d3d012c..5b336e04 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -35,7 +35,6 @@ a work-in-progress.</p>
       <code>-gstabs</code> and <code>-gxcoff</code> options) has been removed.
       (This means the <strong>dbx</strong> debugger is no longer
       supported, either.)</li>
-</li>
 </ul>
  

On 9/5/22 14:31, Gerald Pfeifer wrote:
> On Fri, 26 Aug 2022, Richard Biener via Gcc-patches wrote:
>>> Ready for master?
>> OK
> 
> Actually both Richi and me missed a little detail:
> 
>>> -  <li>...</li>
>>> +    <li>The support for the <code>cr16-elf</code>, <code>tilegx*-linux</code> and <code>tilepro*-linux</code>
>>> +      configurations has been removed.</li>
>>> +</li>                                 ^^^^^
>     ^^^^^

Thanks for the fix. Btw. have you removed the w3c validation script?

Martin

> 
> The patch added one <li> plus two </li>s - fixed thusly.
> 
> Gerald
> 
> 
> commit 0d66c0f73e9c54536070346bd4d52f61132ba012
> Author: Gerald Pfeifer <gerald@pfeifer.com>
> Date:   Mon Sep 5 20:28:57 2022 +0800
> 
>     gcc-13: Remove extraneous </li> under Caveats
>     
>     This snuck in via 79ecba7b which added two </li>s instead of one.
> 
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> index 3d3d012c..5b336e04 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -35,7 +35,6 @@ a work-in-progress.</p>
>        <code>-gstabs</code> and <code>-gxcoff</code> options) has been removed.
>        (This means the <strong>dbx</strong> debugger is no longer
>        supported, either.)</li>
> -</li>
>  </ul>
>  
>
  

On Wed, 7 Sep 2022, Martin Liška wrote:
> Thanks for the fix. Btw. have you removed the w3c validation script?

I didn't remove it, but had to deactive automated notifications since the 
w3.org service started to employ some "are you a secure machine?" checks 
that appear to use Javascript or the like, breaking any automated use of 
that service. :-(

So I literally have to click through notification e-mails and manually 
check the result in the browser; hence the delay.

Gerald
  

On 9/7/22 16:28, Gerald Pfeifer wrote:
> On Wed, 7 Sep 2022, Martin Liška wrote:
>> Thanks for the fix. Btw. have you removed the w3c validation script?
> 
> I didn't remove it, but had to deactive automated notifications since the 
> w3.org service started to employ some "are you a secure machine?" checks 
> that appear to use Javascript or the like, breaking any automated use of 
> that service. :-(

What a pity.

Martin

> 
> So I literally have to click through notification e-mails and manually 
> check the result in the browser; hence the delay.
> 
> Gerald