From: philip.herron@embecosm.com
To: gcc-rust@gcc.gnu.org
Subject: Invitation: Rust community call @ Fri 5 Aug 2022 10am - 10:30am (BST) (gcc-rust@gcc.gnu.org)
Date: Thu, 04 Aug 2022 15:50:29 +0000 [thread overview]
Message-ID: <0000000000000deeff05e56c4f4a@google.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1733 bytes --]
Rust community call
Friday 5 Aug 2022 ⋅ 10am – 10:30am
United Kingdom Time
Location
https://meet.jit.si/gccrs-community-call
https://www.google.com/url?q=https%3A%2F%2Fmeet.jit.si%2Fgccrs-community-call&sa=D&ust=1660060200000000&usg=AOvVaw29X6M4stOtGqtawC0dT9b2
It is time for our next monthly community call:Date: 5th August 2022 at:
09h00 UTCAgenda: https://hackmd.io/ZVgm1LaPQly173-OML2X7QJitsi:
https://meet.jit.si/gccrs-community-call
Organiser
philip.herron@embecosm.com
philip.herron@embecosm.com
Guests
philip.herron@embecosm.com- organiser
gcc-rust@gcc.gnu.org
View all guest info
https://calendar.google.com/calendar/event?action=VIEW&eid=M2Zib3R2b2g3dTE2YnJkdTd0MHZhZnU3dm8gZ2NjLXJ1c3RAZ2NjLmdudS5vcmc&tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb20zNDUwNDU1M2I1Yzc5ZWYxODRlY2U1YTIxZWQ0N2Y5MDUwNWM3OGM2&ctz=Europe%2FLondon&hl=en_GB&es=0
Reply for gcc-rust@gcc.gnu.org and view more details
https://calendar.google.com/calendar/event?action=VIEW&eid=M2Zib3R2b2g3dTE2YnJkdTd0MHZhZnU3dm8gZ2NjLXJ1c3RAZ2NjLmdudS5vcmc&tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb20zNDUwNDU1M2I1Yzc5ZWYxODRlY2U1YTIxZWQ0N2Y5MDUwNWM3OGM2&ctz=Europe%2FLondon&hl=en_GB&es=0
Your attendance is optional.
~~//~~
Invitation from Google Calendar: https://calendar.google.com/calendar/
You are receiving this email because you are an attendee of the event. To
stop receiving future updates for this event, decline this event.
Forwarding this invitation could allow any recipient to send a response to
the organiser, be added to the guest list, invite others regardless of
their own invitation status or modify your RSVP.
Learn more https://support.google.com/calendar/answer/37135#forwarding
[-- Attachment #1.2: Type: text/html, Size: 26786 bytes --]
[-- Attachment #1.3: Type: text/calendar, Size: 1790 bytes --]
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20220805T090000Z
DTEND:20220805T093000Z
DTSTAMP:20220804T155029Z
ORGANIZER;CN=philip.herron@embecosm.com:mailto:philip.herron@embecosm.com
UID:3fbotvoh7u16brdu7t0vafu7vo@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
X-MICROSOFT-CDO-OWNERAPPTID:1802431959
CREATED:20220804T155027Z
DESCRIPTION:<p>It is time for our next monthly community call:</p><ul><li>D
ate: 5th August 2022 at: 09h00 UTC</li><li>Agenda: <a href="https://hackmd.
io/ZVgm1LaPQly173-OML2X7Q" id="ow313" __is_owner="true">https://hackmd.io/Z
Vgm1LaPQly173-OML2X7Q</a></li><li>Jitsi: <a href="https://meet.jit.si/gccrs
-community-call" id="ow320" __is_owner="true">https://meet.jit.si/gccrs-com
munity-call</a></li></ul>\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nDo not edit this section of the
description.\n\nView your event at https://calendar.google.com/calendar/eve
nt?action=VIEW&eid=M2Zib3R2b2g3dTE2YnJkdTd0MHZhZnU3dm8gZ2NjLXJ1c3RAZ2NjLmdu
dS5vcmc&tok=MjYjcGhpbGlwLmhlcnJvbkBlbWJlY29zbS5jb20zNDUwNDU1M2I1Yzc5ZWYxODR
lY2U1YTIxZWQ0N2Y5MDUwNWM3OGM2&ctz=Europe%2FLondon&hl=en_GB&es=1.\n-::~:~::~
:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~
::-
LAST-MODIFIED:20220804T155027Z
LOCATION:https://meet.jit.si/gccrs-community-call
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Rust community call
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR
[-- Attachment #2: invite.ics --]
[-- Type: application/ics, Size: 1829 bytes --]
reply other threads:[~2022-08-04 15:50 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=0000000000000deeff05e56c4f4a@google.com \
--to=philip.herron@embecosm.com \
--cc=gcc-rust@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).