From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Bin.Cheng" <amker.cheng@gmail.com>
Cc: Mateus Carmo Martins de Freitas Barbosa
<mateus.carmo.barbosa@usp.br>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: Rust front-end
Date: Tue, 27 Aug 2019 09:34:00 -0000 [thread overview]
Message-ID: <CAH6eHdQRcGz9b1afKc825U9oD_GejEL3u-vocopDTfJQGvhEwg@mail.gmail.com> (raw)
In-Reply-To: <CAHFci2-XX_qBA1L6u867yQ+HJDEawYoXYFJOWe+-3pX_GKevTg@mail.gmail.com>
On Tue, 27 Aug 2019 at 09:10, Bin.Cheng wrote:
> And couple of words to the community, we may need to be more active in
> order to attract new developers. IMHO, messages asking for information
> shouldn't need one week to be answered?
This is not really the right place to ask for information about
something that isn't part of GCC. Since the Rust front end is
incomplete and not included in the official GCC tree, it would make a
lot more sense to contact the author(s) of that Rust front end.
next prev parent reply other threads:[~2019-08-27 9:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 14:11 Mateus Carmo Martins de Freitas Barbosa
2019-08-27 8:10 ` Bin.Cheng
2019-08-27 9:34 ` Jonathan Wakely [this message]
2019-08-27 14:58 ` David Malcolm
2019-08-30 20:24 ` Mateus Carmo Martins de Freitas Barbosa
2022-06-27 14:51 Philip Herron
2022-06-28 7:30 ` Richard Biener
2022-07-08 17:31 ` Philip Herron
2022-07-11 7:50 ` Richard Biener
2022-07-11 15:01 ` David Edelsohn
2022-10-04 12:29 ` Philip Herron
2022-10-04 12:42 ` David Malcolm
2022-10-04 13:04 ` Jakub Jelinek
2022-10-05 9:39 ` Philip Herron
2022-10-05 9:36 ` Philip Herron
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=CAH6eHdQRcGz9b1afKc825U9oD_GejEL3u-vocopDTfJQGvhEwg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=amker.cheng@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mateus.carmo.barbosa@usp.br \
/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).