public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: arthur.cohen@embecosm.com
To: gcc-rust@gcc.gnu.org
Subject: Invitation: gccrs May community call @ Mon 15 May 2023 11am - 12pm (CEST) (gcc-rust@gcc.gnu.org)
Date: Tue, 02 May 2023 14:53:30 +0000	[thread overview]
Message-ID: <calendar-172c2d64-6675-4eba-9f69-a47a3d1eb357@google.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1471 bytes --]

gccrs May community call
Monday 15 May 2023 ⋅ 11am – 12pm
Central European Time - Paris



https://meet.jit.si/gccrs-community-call-may

Guests
gcc-rust@gcc.gnu.org
View all guest info  
https://calendar.google.com/calendar/event?action=VIEW&eid=Nzc5cW42ODZ2a3VwYW00Nm9lOXB2NWYydTYgZ2NjLXJ1c3RAZ2NjLmdudS5vcmc&tok=OTAjNzA2MGEwOTIzZmZlYmQzY2I1MmIxYWZlZjM1YTI4ZmY3YjY0ZjA1OTYyYzlhZjg0YzIzYjE4NDdmMWY1Zjg5NEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNzFlMGNhZWVhMWM3ZTE4ODM4OWQzOTZhZmNhMmJiMmQ0ZTA5YWUyMg&ctz=Europe%2FParis&hl=en&es=0

Reply for gcc-rust@gcc.gnu.org and view more details  
https://calendar.google.com/calendar/event?action=VIEW&eid=Nzc5cW42ODZ2a3VwYW00Nm9lOXB2NWYydTYgZ2NjLXJ1c3RAZ2NjLmdudS5vcmc&tok=OTAjNzA2MGEwOTIzZmZlYmQzY2I1MmIxYWZlZjM1YTI4ZmY3YjY0ZjA1OTYyYzlhZjg0YzIzYjE4NDdmMWY1Zjg5NEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNzFlMGNhZWVhMWM3ZTE4ODM4OWQzOTZhZmNhMmJiMmQ0ZTA5YWUyMg&ctz=Europe%2FParis&hl=en&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 on 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 organizer, 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/calendar, Size: 1218 bytes --]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Europe/Paris
X-LIC-LOCATION:Europe/Paris
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Europe/Paris:20230515T110000
DTEND;TZID=Europe/Paris:20230515T120000
DTSTAMP:20230502T145330Z
ORGANIZER;CN=gccrs:mailto:7060a0923ffebd3cb52b1afef35a28ff7b64f05962c9af84c
 23b1847f1f5f894@group.calendar.google.com
UID:779qn686vkupam46oe9pv5f2u6@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
X-MICROSOFT-CDO-OWNERAPPTID:417312626
CREATED:20230502T145329Z
DESCRIPTION:<a href="https://meet.jit.si/gccrs-community-call-may">https://
 meet.jit.si/gccrs-community-call-may</a>
LAST-MODIFIED:20230502T145329Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:gccrs May community call
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

[-- Attachment #2: invite.ics --]
[-- Type: application/ics, Size: 1262 bytes --]

                 reply	other threads:[~2023-05-02 14:53 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=calendar-172c2d64-6675-4eba-9f69-a47a3d1eb357@google.com \
    --to=arthur.cohen@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).