From: philip.herron@embecosm.com
To: gcc-rust@gcc.gnu.org, arthur.cohen@embecosm.com, philipp@recogni.com
Subject: Updated invitation: Rust GCC community call @ Fri 10 Jun 2022 10am - 10:30am (BST) (gcc-rust@gcc.gnu.org)
Date: Tue, 07 Jun 2022 09:00:13 +0000 [thread overview]
Message-ID: <0000000000001255f705e0d7d1b7@google.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1681 bytes --]
This event has been changed.
Title: Rust GCC community call
Hi everyoneIts that time again for the community call:Date and Time 10th
June 2022 at: Fri, Jun 10 2022, 10:00
UTCAgenda: https://hackmd.io/xWN5fFdWTPWgFa-Tny-jNg please feel
free to add agenda items you wish to see
discussed.Jitsi: https://meet.jit.si/gccrs-community-callThanks--Phil
When: Fri 10 Jun 2022 10am – 10:30am United Kingdom Time (changed)
Where: https://meet.jit.si/gccrs-community-call
Calendar: gcc-rust@gcc.gnu.org
Who:
* philip.herron@embecosm.com- organiser
* gcc-rust@gcc.gnu.org
* arthur.cohen@embecosm.com
* philipp@recogni.com
Event details:
https://calendar.google.com/calendar/event?action=VIEW&eid=MmhxdXZyMWFsZmY0a2Eya2k3NmM5M3EyODggZ2NjLXJ1c3RAZ2NjLmdudS5vcmc&tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb21kYzU5YTM1MjMwZTQ1ZjE1MmYwYTkxZTQ5M2RlOWExODA3NmQwMTU5&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: 11755 bytes --]
[-- Attachment #1.3: Type: text/calendar, Size: 2506 bytes --]
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20220610T090000Z
DTEND:20220610T093000Z
DTSTAMP:20220607T090013Z
ORGANIZER;CN=philip.herron@embecosm.com:mailto:philip.herron@embecosm.com
UID:2hquvr1alff4ka2ki76c93q288@google.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
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=arthur.cohen@embecosm.com;X-NUM-GUESTS=0:mailto:arthur.cohen@embeco
sm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=philipp@recogni.com;X-NUM-GUESTS=0:mailto:philipp@recogni.com
X-MICROSOFT-CDO-OWNERAPPTID:-273159294
CREATED:20220607T090001Z
DESCRIPTION:<span>Hi everyone<br><br></span><br><span>Its that time again f
or the community call:<br></span><br><span><br>Date and Time 10th June 2022
at:<span> \;</span></span><time><span> \;</span>Fri\, Jun 10 2022\
, 10:00 UTC</time><br><span>Agenda:<span> \;</span></span><a href="http
s://hackmd.io/xWN5fFdWTPWgFa-Tny-jNg" id="ow338" __is_owner="true">https://
hackmd.io/xWN5fFdWTPWgFa-Tny-jNg</a><span><span> \;</span>please feel f
ree to add agenda items you wish to see discussed.</span><br><span>Jitsi:<s
pan> \;</span></span><a href="https://meet.jit.si/gccrs-community-call"
id="ow342" __is_owner="true">https://meet.jit.si/gccrs-community-call<br><
br></a><br>Thanks<br><br>--Phil<br><a href="https://meet.jit.si/gccrs-commu
nity-call" id="ow342" __is_owner="true"></a>\n\n-::~:~::~:~:~:~:~:~:~:~:~:~
:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nDo not edit t
his section of the description.\n\nView your event at https://calendar.goog
le.com/calendar/event?action=VIEW&eid=MmhxdXZyMWFsZmY0a2Eya2k3NmM5M3EyODggZ
2NjLXJ1c3RAZ2NjLmdudS5vcmc&tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb21kYzU5
YTM1MjMwZTQ1ZjE1MmYwYTkxZTQ5M2RlOWExODA3NmQwMTU5&ctz=Europe%2FLondon&hl=en_
GB&es=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20220607T090012Z
LOCATION:https://meet.jit.si/gccrs-community-call
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Rust GCC community call
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR
[-- Attachment #2: invite.ics --]
[-- Type: application/ics, Size: 2555 bytes --]
reply other threads:[~2022-06-07 9:00 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=0000000000001255f705e0d7d1b7@google.com \
--to=philip.herron@embecosm.com \
--cc=arthur.cohen@embecosm.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=philipp@recogni.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).