From: Jason Merrill <jason@redhat.com>
To: Philip Herron <philip.herron@embecosm.com>
Cc: gcc Mailing List <gcc@gcc.gnu.org>,
Overseers mailing list <overseers@sourceware.org>
Subject: Re: GCC Rust git branch
Date: Thu, 27 May 2021 23:22:03 -0400 [thread overview]
Message-ID: <CADzB+2=63yKAj0GAq6XN+v+U+6g0VzHcEbm1VfYx_Vdg4UB1hg@mail.gmail.com> (raw)
In-Reply-To: <5b2057ae-039c-6805-20fe-133df71c120e@embecosm.com>
On Mon, May 24, 2021 at 9:25 AM Philip Herron <philip.herron@embecosm.com>
wrote:
> Hi everyone,
>
> As some of you might know, I have been working on GCC Rust over on
> GitHub https://github.com/Rust-GCC/gccrs. As the project is moving
> forward and enforcing GCC copyright assignments for contributors, I
> would like to create a branch on the GCC git repo to show the intention
> to be upstream with GCC someday.
>
[snip]
Separately, some contributors have expressed interest in maintaining the
> GCC style communications of using a mailing list and irc. Is it
> reasonable for this project to get a rust@gcc.gnu.org?
>
That makes sense to me; I think overseers@ can help set up a new mailing
list.
Jason
next prev parent reply other threads:[~2021-05-28 3:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 13:24 Philip Herron
2021-05-24 16:24 ` Joseph Myers
2022-06-08 12:36 ` Thomas Schwinge
2021-05-24 18:29 ` Mark Wielaard
2021-05-28 10:31 ` Philip Herron
2021-05-30 22:33 ` Mark Wielaard
2021-05-28 3:05 ` Thomas Fitzsimmons
2021-05-28 10:18 ` Philip Herron
2021-05-28 11:48 ` Marc Poulhiès
2021-05-30 22:49 ` Mark Wielaard
2021-05-28 3:22 ` Jason Merrill [this message]
2021-05-28 10:19 ` Philip Herron
2022-06-08 10:58 ` Document <gcc-rust@gcc.gnu.org> mailing list (was: GCC Rust git branch) Thomas Schwinge
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='CADzB+2=63yKAj0GAq6XN+v+U+6g0VzHcEbm1VfYx_Vdg4UB1hg@mail.gmail.com' \
--to=jason@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=overseers@sourceware.org \
--cc=philip.herron@embecosm.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).