public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Philip Herron <philip.herron@embecosm.com>
To: gcc Mailing List <gcc@gcc.gnu.org>, gcc-rust@gcc.gnu.org
Subject: Re: GCC Rust monthly call
Date: Fri, 4 Jun 2021 11:47:06 +0100	[thread overview]
Message-ID: <CAB2u+n0cUDY1vdXB5PWgfa2knSLa8kC=HYGErHFgVHq8B5j6kA@mail.gmail.com> (raw)
In-Reply-To: <CAB2u+n2m2A0O1i8PFa3gdc08wCaw2LOOgoE-0NnA4R8drEDQAw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]

Hi everyone,

For those interested, you find the meeting notes of our call over on:
https://github.com/Rust-GCC/Reporting/blob/main/2021-06-04-community-call.md

Thanks,

--Phil

On Thu, 3 Jun 2021 at 12:33, Philip Herron <philip.herron@embecosm.com>
wrote:

> Hi everyone,
>
> Just a reminder that tomorrow is the community call: at 10am utc+1. The
> agenda so far is detailed within: https://hackmd.io/rBFlwl_9TkWLox-X6jyxDg
>
> The call will be hosted on Jitsi, here is the link we will use:
> https://meet.jit.si/259057065581073
>
> Thanks
>
> --Phil
>
> On Mon, 31 May 2021 at 12:48, Philip Herron <philip.herron@embecosm.com>
> wrote:
>
>> Hello,
>>
>> On the first Friday of every month, GCC Rust has a community call. The
>> next one will be on the 4th of June 2021, at 10am utc+1 (I am based in
>> Northern Ireland). We use our zulip server
>> (https://gcc-rust.zulipchat.com/), which provides a jitsi integration to
>> facilitate the video call. I want to invite people from the GCC
>> community to join if they wish.
>>
>> These monthly calls have associated meeting notes for those who cannot
>> attend. Here is an example from our last meeting:
>>
>> https://github.com/Rust-GCC/Reporting/blob/main/2021-05-07-community-call.md
>>
>> The agenda for this next call is currently being set up in a
>> collaborative document here: https://hackmd.io/rBFlwl_9TkWLox-X6jyxDg
>>
>> Please find the monthly report for May 2021 for more information:
>> https://github.com/Rust-GCC/Reporting/blob/main/2021-05-monthly-report.org
>>
>> Thanks
>>
>> --Phil
>>
>>

[-- Attachment #2: Type: text/html, Size: 2984 bytes --]

  reply	other threads:[~2021-06-04 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53b287c0-a6df-2fb7-e37f-764928253477@embecosm.com>
2021-06-03 11:33 ` Philip Herron
2021-06-04 10:47   ` Philip Herron [this message]
2021-06-04 10:48     ` John Paul Adrian Glaubitz
2021-06-04 10:54       ` Philip Herron
2021-06-04 11:01         ` John Paul Adrian Glaubitz

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+n0cUDY1vdXB5PWgfa2knSLa8kC=HYGErHFgVHq8B5j6kA@mail.gmail.com' \
    --to=philip.herron@embecosm.com \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=gcc@gcc.gnu.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).