public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Gaius Mulley <gaiusmod2@gmail.com>
Cc: gcc-patches@gcc.gnu.org,
	Richard Guenther <richard.guenther@gmail.com>,
	 Jakub Jelinek <jakub@redhat.com>
Subject: Re: [wwwdocs] document modula-2 in gcc-13/changes.html (and index.html)
Date: Sat, 4 Mar 2023 08:14:17 +0100 (CET)	[thread overview]
Message-ID: <06a0d2f2-eb63-82b3-bcd9-b211b39ffed3@pfeifer.com> (raw)
In-Reply-To: <87bkm7xdda.fsf@debian>

Hi Gaius,

apologies, I thought you had pushed the updated patch and only now 
realized it's not in yet.

Please look into the few bits below and then go ahead and push.

On Mon, 6 Feb 2023, Gaius Mulley wrote:
> 	* htdocs/frontends.html: An update to say the front end is now in
> 	the development trunk.

Here we'd usually simply say

  * frontends: The Modula-2 front end is now on the 
  development trunk.

skiping "An update to say", or at least "An update to" and the "htdocs/" 
port (and adding which front end).

> 	* htdocs/gcc-13/changes.html: A description of which dialects are
> 	supported and the user level front end changes so far.

  * gcc-13: Note which Modula-2 dialects are...

> 	* htdocs/index.html: Proposed news entry.

  * index: Announce Modula-2 inclusion 

(or something like that).

> 	* htdocs/onlinedocs/index.html: PDF, PS and HTML documentation
> 	links.
  * onlinedocs: Add links to Modula-2 documentation


> +The compiler is operational with GCC 10, GCC 11 GCC 12 (on
                                   
...GCC 11, and GCC 12...

> +GNU/Linux x86 systems).  The front end is now in the GCC development
> +trunk (GCC 13).  The front end is mostly written in Modula-2 and it
>  includes a bootstrap tool which translates Modula-2 into C/C++.</li>

How about "It is mostly written in Modula-2 and includes..." to avoid
repetition of "the front end"?


Thank you,
Gerald

  reply	other threads:[~2023-03-04  7:14 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
2023-02-06 11:05   ` Gaius Mulley
2023-03-04  7:14     ` Gerald Pfeifer [this message]
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=06a0d2f2-eb63-82b3-bcd9-b211b39ffed3@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gaiusmod2@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --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).