From: philip.herron@embecosm.com
To: gcc-rust@gcc.gnu.org, arthur.cohen@embecosm.com
Cc: philipp.krones@embecosm.com, jeremy.bennett@embecosm.com,
simon.cook@embecosm.com
Subject: Invitation: GCC Rust Community Call @ Fri 4 Mar 2022 2pm - 2:30pm (GMT) (gcc-rust@gcc.gnu.org)
Date: Tue, 01 Mar 2022 17:28:05 +0000 [thread overview]
Message-ID: <000000000000e6915d05d92b7c23@google.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1716 bytes --]
You have been invited to the following event.
Title: GCC Rust Community Call
Hi everyone,Its that time again:- Date and Time 4th March 2022 at:14h00
UTC- Agenda: https://hackmd.io/KkrXwApIQgWwaUL8fl1Yrg?both- Jitsi:
https://meet.jit.si/ArtificialPantsFlashNeitherHope everyone has a great
week.Thanks--Phil
When: Fri 4 Mar 2022 2pm – 2:30pm United Kingdom Time
Where: https://meet.jit.si/ArtificialPantsFlashNeither
Calendar: gcc-rust@gcc.gnu.org
Who:
* philip.herron@embecosm.com- organiser
* gcc-rust@gcc.gnu.org
* arthur.cohen@embecosm.com
* philipp.krones@embecosm.com - optional
* jeremy.bennett@embecosm.com - optional
* simon.cook@embecosm.com - optional
Event details:
https://calendar.google.com/calendar/event?action=VIEW&eid=N2dvb3V0czR1ZjY1Nmc2aWMwb2Y0aHB0MHIgZ2NjLXJ1c3RAZ2NjLmdudS5vcmc&tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb205YTE1YTZjNmM1NGVkNjcwMjM1MjU0MzQ5NmVmZWMzMjJiZDY0NGQz&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: 12685 bytes --]
[-- Attachment #1.3: Type: text/calendar, Size: 2366 bytes --]
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20220304T140000Z
DTEND:20220304T143000Z
DTSTAMP:20220301T172805Z
ORGANIZER;CN=philip.herron@embecosm.com:mailto:philip.herron@embecosm.com
UID:7goouts4uf656g6ic0of4hpt0r@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=OPT-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=arthur.cohen@embecosm.com;X-NUM-GUESTS=0:mailto:arthur.cohen@embeco
sm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=jeremy.bennett@embecosm.com;X-NUM-GUESTS=0:mailto:jeremy.bennett@em
becosm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=simon.cook@embecosm.com;X-NUM-GUESTS=0:mailto:simon.cook@embecosm.c
om
X-MICROSOFT-CDO-OWNERAPPTID:-1148383427
CREATED:20220301T172804Z
DESCRIPTION:Hi everyone\,<br><br>Its that time again:<br><br>- Date and Tim
e 4th March 2022 at:14h00 UTC<br><br>- Agenda: https://hackmd.io/KkrXwApIQg
WwaUL8fl1Yrg?both<br>- Jitsi: <span><span>https://meet.jit.si/ArtificialPan
tsFlashNeither</span></span><br><br>Hope everyone has a great week.<br><br>
Thanks<br><br>--Phil\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nDo not edit this section of the descr
iption.\n\nView your event at https://calendar.google.com/calendar/event?ac
tion=VIEW&eid=N2dvb3V0czR1ZjY1Nmc2aWMwb2Y0aHB0MHIgZ2NjLXJ1c3RAZ2NjLmdudS5vc
mc&tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb205YTE1YTZjNmM1NGVkNjcwMjM1MjU0
MzQ5NmVmZWMzMjJiZDY0NGQz&ctz=Europe%2FLondon&hl=en_GB&es=1.\n-::~:~::~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20220301T172804Z
LOCATION:https://meet.jit.si/ArtificialPantsFlashNeither
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:GCC Rust Community Call
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR
[-- Attachment #2: invite.ics --]
[-- Type: application/ics, Size: 2415 bytes --]
reply other threads:[~2022-03-01 17:28 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=000000000000e6915d05d92b7c23@google.com \
--to=philip.herron@embecosm.com \
--cc=arthur.cohen@embecosm.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=jeremy.bennett@embecosm.com \
--cc=philipp.krones@embecosm.com \
--cc=simon.cook@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).