From: Gerald Pfeifer <gerald@pfeifer.com>
To: Gaius Mulley <gaiusmod2@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Richard Guenther <richard.guenther@gmail.com>
Subject: Re: [wwwdocs] document modula-2 in gcc-13/changes.html (and index.html)
Date: Fri, 3 Feb 2023 20:18:57 +0100 (CET) [thread overview]
Message-ID: <8bb9f1fc-95e8-ebe4-3d87-b3ec28c99add@pfeifer.com> (raw)
In-Reply-To: <87lelels1w.fsf@debian>
On Fri, 3 Feb 2023, Gaius Mulley wrote:
> The following patch provides a summary of the modula-2 front end
> and also contains links to the online modula-2 documentation in
> index.html.
> +<h3 id="modula2">Modula-2</h3>
> +<ul>
> + <li>Support for the language Modula-2 has been added. The dialects
> + supported are PIM2, PIM3, PIM4 and ISO/IEC 10514-1. Also included
> + are a complete set of ISO/IEC 10514-1 libraries and PIM
> + libraries.</li>
I wonder whether we can this a bit more active.
Maybe something like "This includes support for the ... dialects, a
complete set of ...and ..."?
> + <li><a href="https://gcc.gnu.org/onlinedocs/m2/Compiler-options.html">
> + Compiler options</a>.</li>
Maybe put this in parenthesis since it's not an update as such and more
relatives to the previous item?
> + <li>Linking has been redesigned.</li>
What are we saying here? I.e., what is the change we are announcing? As a
user, what might I notice? Why do I care?
The above are questions to possibly improve this for our users. Please
adjust as you see fit, or push as is, if you prefer.
On a somewhat related note: This is definitely big enough to warrant an
entry in the News section on our main page. :-) Do you want to propose
something?
Gerald
next prev parent reply other threads:[~2023-02-03 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 14:52 Gaius Mulley
2023-02-03 15:28 ` Jakub Jelinek
2023-02-03 19:18 ` Gerald Pfeifer [this message]
2023-02-06 11:05 ` Gaius Mulley
2023-03-04 7:14 ` Gerald Pfeifer
2023-03-06 11:40 ` Gaius Mulley
2023-03-15 22:51 ` Gerald Pfeifer
2023-03-16 4:40 ` Gaius Mulley
2023-03-16 23:22 ` Gerald Pfeifer
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=8bb9f1fc-95e8-ebe4-3d87-b3ec28c99add@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).