From: Thomas Schwinge <thomas@codesourcery.com>
To: Philip Herron <philip.herron@embecosm.com>,
<gcc-rust@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>
Cc: <gcc@gcc.gnu.org>, <overseers@sourceware.org>,
Jason Merrill <jason@redhat.com>
Subject: Document <gcc-rust@gcc.gnu.org> mailing list (was: GCC Rust git branch)
Date: Wed, 8 Jun 2022 12:58:03 +0200 [thread overview]
Message-ID: <87edzzqv5w.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <41c2376e-3b0e-7e32-5094-468caa692138@embecosm.com>
[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]
Hi!
On 2021-05-28T11:19:16+0100, Philip Herron <philip.herron@embecosm.com> wrote:
> On 28/05/2021 04:22, Jason Merrill wrote:
>> On Mon, May 24, 2021 at 9:25 AM Philip Herron <philip.herron@embecosm.com <mailto:philip.herron@embecosm.com>> wrote:
>>> As some of you might know, I have been working on GCC Rust over on
>>> GitHub https://github.com/Rust-GCC/gccrs
>>> <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
>>> <mailto:rust@gcc.gnu.org>?
>>
>> That makes sense to me; I think overseers@ can help set up a new
>> mailing list.
>
> Thanks For the info everyone i will reach out to overseers about the
> Mailing List idea.
A <gcc-rust@gcc.gnu.org> mailing list has thus been set up a year ago;
now documented on <https://gcc.gnu.org/lists.html> per gcc-wwwdocs
commit 1c89cdccbebda5d4c2eeeb627b1461b8877bb27e
"Document <gcc-rust@gcc.gnu.org> mailing list", see attached.
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Document-gcc-rust-gcc.gnu.org-mailing-list.patch --]
[-- Type: text/x-diff, Size: 1070 bytes --]
From 1c89cdccbebda5d4c2eeeb627b1461b8877bb27e Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <thomas@codesourcery.com>
Date: Wed, 8 Jun 2022 12:55:55 +0200
Subject: [PATCH] Document <gcc-rust@gcc.gnu.org> mailing list
---
htdocs/lists.html | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/htdocs/lists.html b/htdocs/lists.html
index ad36a7e2..c32c505d 100644
--- a/htdocs/lists.html
+++ b/htdocs/lists.html
@@ -70,6 +70,11 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
is a moderate volume list where regression results for the GCC compilers
are posted.</li>
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-rust/">gcc-rust</a></b>
+ is for discussing <a href="https://gcc.gnu.org/wiki/RustFrontEnd">Rust
+ support in GCC</a>.
+ Patches should be sent to both this list and <b>gcc-patches</b>.</li>
+
<li><b><a href="https://gcc.gnu.org/ml/libstdc++/">libstdc++</a></b>
is the main discussion and development list for the standard C++
library (libstdc++-v3). Patches to libstdc++-v3 should be sent to
--
2.35.1
next parent reply other threads:[~2022-06-08 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5b2057ae-039c-6805-20fe-133df71c120e@embecosm.com>
[not found] ` <CADzB+2=63yKAj0GAq6XN+v+U+6g0VzHcEbm1VfYx_Vdg4UB1hg@mail.gmail.com>
[not found] ` <41c2376e-3b0e-7e32-5094-468caa692138@embecosm.com>
2022-06-08 10:58 ` Thomas Schwinge [this message]
[not found] ` <alpine.DEB.2.22.394.2105241618020.247381@digraph.polyomino.org.uk>
2022-06-08 12:36 ` 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=87edzzqv5w.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--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).