From: Iain Buclaw <ibuclaw@gdcproject.org>
To: gerald@pfeifer.com
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] Add D language to news, frontends, release notes, and readings.
Date: Sun, 02 Dec 2018 20:17:00 -0000 [thread overview]
Message-ID: <CABOHX+f-_6j3YbP27X4sZuyXRmrmO9sUhM+Ao+r0z1+BPfGmxw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1812021816050.3833@anthias.pfeifer.com>
On Sun, 2 Dec 2018 at 18:23, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> Hi Iain,
>
> On Mon, 12 Nov 2018, Iain Buclaw wrote:
> > As suggested, this adds an announcement of the D front end addition
> > to the news items on the GCC home page, and from what I can tell, the
> > relevant pages where the language should get a mention.
>
> I noticed this hasn't gone in; apologies for missing it. (You are
> welcome, though should not have to, copy me on wwwdocs changes, which
> usually helps a bit, though also others can approve those.)
>
> > Kept the release notes brief for now, will expand later. Is this OK?
>
> Yes, just a minor nit:
>
> Index: htdocs/gcc-9/changes.html
> ===================================================================
> +<h3 id="d">D</h3>
> +<ul>
> + <li>Support for the D programming language has been added to GCC,
> + implementing version 2.076 of the language and runtime library.
>
> "run-time library" here, per codingconventions.html .
>
Hi Gerald,
OK, thanks I'll do that.
I assume that the notes on the about.html page are all that are needed
to commit and push?
--
Iain
next prev parent reply other threads:[~2018-12-02 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 22:58 Iain Buclaw
2018-12-02 17:23 ` Gerald Pfeifer
2018-12-02 20:17 ` Iain Buclaw [this message]
2018-12-02 21:34 ` Gerald Pfeifer
2018-12-03 16:50 ` Iain Buclaw
2018-12-07 22:46 ` Iain Buclaw
2018-12-07 22:56 ` 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=CABOHX+f-_6j3YbP27X4sZuyXRmrmO9sUhM+Ao+r0z1+BPfGmxw@mail.gmail.com \
--to=ibuclaw@gdcproject.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).