public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Philip Herron <philip.herron@embecosm.com>
To: Mark Wielaard <mark@klomp.org>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: Sourceware accepted as SFC member project
Date: Fri, 9 Sep 2022 11:11:56 +0100	[thread overview]
Message-ID: <CAB2u+n2Yoa_06c+2UgtXC8jfyO01kVdGNHDAXC6-e-A09bb33A@mail.gmail.com> (raw)
In-Reply-To: <YxpziWafU0BiZXgZ@wildebeest.org>

Hi Mark

Do you have the link available to join this mailing list? I am
interested to see how this goes, the SFC is a great organization. I
love the idea of it for gccrs but not sure how that would affect
interaction with GCC.

I hope you are doing well.

--Phil

On Thu, 8 Sept 2022 at 23:58, Mark Wielaard <mark@klomp.org> wrote:
>
> Hi,
>
> We are very grateful for the public replies and suggestions received
> to our proposal, which were all very positive. And we are happy to
> report that the SFC's Evaluations Committee has voted to accept
> Sourceware as a Conservancy member project. If people are interested
> in, or want to help out with, the next steps they are invited to join
> the sourceware overseers list.
>
> https://sourceware.org/pipermail/overseers/2022q3/018834.html
>
> Thanks,
>
> Chris Faylor <cgf@sourceware.org>
> Frank Eigler <fche@sourceware.org>
> Mark Wielaard <mark@klomp.org>
> --
> Gcc-rust mailing list
> Gcc-rust@gcc.gnu.org
> https://gcc.gnu.org/mailman/listinfo/gcc-rust

  reply	other threads:[~2022-09-09 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 18:49 Proposing Sourceware " Mark Wielaard
2022-09-08 22:58 ` Sourceware accepted " Mark Wielaard
2022-09-09 10:11   ` Philip Herron [this message]
2022-09-09 10:40     ` Mark Wielaard
2022-11-15 21:46   ` Sourceware infrastructure presentation and community Q&A Mark Wielaard
2022-12-31 22:57     ` Mark Wielaard

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=CAB2u+n2Yoa_06c+2UgtXC8jfyO01kVdGNHDAXC6-e-A09bb33A@mail.gmail.com \
    --to=philip.herron@embecosm.com \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=mark@klomp.org \
    /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).