Thanks @pauamma. I have just fixed the issues: I am waiting for @gerald to give a look as well before committing it, so it makes sense to fix them already in the review.

This revision now requires review to proceed.Mar 6 2023, 10:51 AM

Harbormaster completed remote builds in B50164: Diff 118373.Mar 6 2023, 10:51 AM

English LGTM.

This revision is now accepted and ready to land.Mar 6 2023, 2:50 PM

gerald requested changes to this revision.Mar 7 2023, 9:07 AM

gerald added inline comments.

website/content/en/status/report-2023-01-2023-03/gcc.adoc
16	several? (Many sounds like a lot. :-) )
17	...to either update to use a supported GCC release or deprecate.
19	...ports contributors who have been helping. (or: are helping) Just quite shorter. :-)
25	How about making this "Very few ports require a specific version of GCC with USE_GCC=11 or similar"? The current text is correct, just the intention and status probably are better reflected that way?

This revision now requires changes to proceed.Mar 7 2023, 9:07 AM

I have followed all @gerald's suggestions except the last one (please see inline reply comment).

Harbormaster completed remote builds in B50186: Diff 118449.Mar 7 2023, 1:34 PM

salvadore added inline comments.Mar 7 2023, 1:39 PM

website/content/en/status/report-2023-01-2023-03/gcc.adoc
25	I prefer how I have written it. My intention here is to inform all ports maintainers and committers that they cannot use the `USE_GCC=X+` construct anymore. If someone have worked in the ports tree for a long time, remembers `USE_GCC=X+`, and is tempted to introduce it in some port, this sentence should warn against it.