From: philip.herron@embecosm.com
To: gcc-rust@gcc.gnu.org, arthur.cohen@embecosm.com,
philipp.krones@embecosm.com
Subject: Invitation: GCC Rust community-call @ Fri 13 May 2022 10am - 10:30am (BST) (gcc-rust@gcc.gnu.org)
Date: Wed, 11 May 2022 12:36:44 +0000 [thread overview]
Message-ID: <000000000000a90eb505debbb117@google.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2149 bytes --]
You have been invited to the following event.
Title: GCC Rust community-call
Hi allIt's that time again for our community call this Friday. Date and
Time 13th May 2022 at: 09h00 UTCAgenda:
https://hackmd.io/ljuSwxP2Qn-oKf5jF_V2UA please feel free to add agenda
items you wish to see discussed.Jitsi:
https://meet.jit.si/gccrs-community-call This moves the call back to
our old time slot which seems to suit people better. In order to
accommodate our friends in the US timezone, I will be hosting a separate
call on Wednesday, details will be announced for that in the next
report. Thanks--Phil
When: Fri 13 May 2022 10am – 10:30am United Kingdom Time
Where: https://meet.jit.si/gccrs-community-call
Joining info: Join with Google Meet
https://meet.google.com/hae-xskw-ces?hs=224
Join by phone
(GB) +44 20 3956 9493 (PIN: 263965918)
More phone numbers: https://tel.meet/hae-xskw-ces?pin=6346729388270&hs=0
Calendar: gcc-rust@gcc.gnu.org
Who:
* philip.herron@embecosm.com- organiser
* arthur.cohen@embecosm.com
* philipp.krones@embecosm.com
* gcc-rust@gcc.gnu.org
Event details:
https://calendar.google.com/calendar/event?action=VIEW&eid=NnFrOHNqdDF0Y3A1OGxhOWtibGV0M2FuaDEgZ2NjLXJ1c3RAZ2NjLmdudS5vcmc&tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb20zOTNkYmIwMjgwZWMzNjA4ZTA1ZjFmMWM3MzE3MmQxMmNiZmJhZGE2&ctz=Europe%2FLondon&hl=en_GB&es=0
Invitation from Google Calendar: https://calendar.google.com/calendar/
You are receiving this courtesy email at the account gcc-rust@gcc.gnu.org
because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively, you can sign up for a Google Account at
https://calendar.google.com/calendar/ and control your notification
settings for your entire calendar.
Forwarding this invitation could allow any recipient to send a response to
the organiser and be added to the guest list, invite others regardless of
their own invitation status or to modify your RSVP. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
[-- Attachment #1.2: Type: text/html, Size: 14781 bytes --]
[-- Attachment #1.3: Type: text/calendar, Size: 2780 bytes --]
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20220513T090000Z
DTEND:20220513T093000Z
DTSTAMP:20220511T123644Z
ORGANIZER;CN=philip.herron@embecosm.com:mailto:philip.herron@embecosm.com
UID:6qk8sjt1tcp58la9kblet3anh1@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=arthur.cohen@embecosm.com;X-NUM-GUESTS=0:mailto:arthur.cohen@embeco
sm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=philip.herron@embecosm.com;X-NUM-GUESTS=0:mailto:philip.herron@embecosm
.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=philipp.krones@embecosm.com;X-NUM-GUESTS=0:mailto:philipp.krones@em
becosm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=gcc-rust@gcc.gnu.org;X-NUM-GUESTS=0:mailto:gcc-rust@gcc.gnu.org
X-GOOGLE-CONFERENCE:https://meet.google.com/hae-xskw-ces
X-MICROSOFT-CDO-OWNERAPPTID:-445955300
CREATED:20220511T123643Z
DESCRIPTION:Hi all<br><br>It's that time again for our community call this
Friday. <br><ul dir="auto"><li>Date and Time 13th May 2022 at: 09h00 UTC</l
i><li>Agenda: <a href="https://hackmd.io/ljuSwxP2Qn-oKf5jF_V2UA">https://ha
ckmd.io/ljuSwxP2Qn-oKf5jF_V2UA</a> please feel free to add agenda items you
wish to see discussed.</li><li>Jitsi: <span><span><a href="https://meet.ji
t.si/gccrs-community-call" id="ow1696" __is_owner="true">https://meet.jit.s
i/gccrs-community-call</a> \;</span></span></li></ul><br>This moves the
call back to our old time slot which seems to suit people better. In order
to accommodate our friends in the US timezone\, I will be hosting a separa
te call on Wednesday\, details will be announced for that in the next repor
t. \; <br> \;<br>Thanks<br><br>--Phil\n\n-::~:~::~:~:~:~:~:~:~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nDo not edit
this section of the description.\n\nThis event has a video call.\nJoin: htt
ps://meet.google.com/hae-xskw-ces\n(GB) +44 20 3956 9493 PIN: 263965918#\nV
iew more phone numbers: https://tel.meet/hae-xskw-ces?pin=6346729388270&hs=
7\n\nView your event at https://calendar.google.com/calendar/event?action=V
IEW&eid=NnFrOHNqdDF0Y3A1OGxhOWtibGV0M2FuaDEgZ2NjLXJ1c3RAZ2NjLmdudS5vcmc&tok
=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb20zOTNkYmIwMjgwZWMzNjA4ZTA1ZjFmMWM3Mz
E3MmQxMmNiZmJhZGE2&ctz=Europe%2FLondon&hl=en_GB&es=1.\n-::~:~::~:~:~:~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20220511T123643Z
LOCATION:https://meet.jit.si/gccrs-community-call
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:GCC Rust community-call
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR
[-- Attachment #2: invite.ics --]
[-- Type: application/ics, Size: 2833 bytes --]
reply other threads:[~2022-05-11 12:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000a90eb505debbb117@google.com \
--to=philip.herron@embecosm.com \
--cc=arthur.cohen@embecosm.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=philipp.krones@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).