public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH,WWWDOCS] htdocs: news: GCC BPF in Compiler Explorer
Date: Thu, 12 Jan 2023 14:50:10 +0100	[thread overview]
Message-ID: <871qnzq2ul.fsf@oracle.com> (raw)
In-Reply-To: <2712211e-92e4-8530-3fb0-5844f89428dc@pfeifer.com> (Gerald Pfeifer's message of "Wed, 11 Jan 2023 15:21:52 +0100 (CET)")


> On Fri, 23 Dec 2022, Jose E. Marchesi via Gcc-patches wrote:
>> This patch adds an entry to the News section in index.html, announcing
>> the availability of a nightly build of bpf-unknown-none-gcc.
>
> Nice!
>
>> +<dt><span><a href="https://godbolt.org">GCC BPF in Compiler Explorer</a></span>
>> +     <span class="date">[2022-12-23]</span></dt>
>> +<dd>Support for a nightly build of the bpf-unknown-none-gcc compiler
>> +  has been contributed to Compiler Explorer (aka godbolt.org) by Marc
>> +  Poulhiès</dd>
>
> Usually I recommend active voice, something like "Compiler Explorer (aka 
> godbolt.org) now supports nightly builds of the bpf-unknown-none-gcc 
> compiler thanks to Marc Poulhiès", but your proposal is perfectly fine, 
> too.
>
> Which means only change if you like the alternative apprach better 
> yourself; otherwise simply use the existing one.
>
> Either way: Okay, and thank you!

Committed, thanks.

      reply	other threads:[~2023-01-12 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23  9:33 Jose E. Marchesi
2023-01-11 14:21 ` Gerald Pfeifer
2023-01-12 13:50   ` Jose E. Marchesi [this message]

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=871qnzq2ul.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --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).