public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: philip.herron@embecosm.com
To: gcc-rust@gcc.gnu.org
Subject: Cancelled event with note: GCC Rust hang out @ Wed 13 Jul 2022 7pm - 7:30pm (BST) (gcc-rust@gcc.gnu.org)
Date: Wed, 13 Jul 2022 16:45:48 +0000	[thread overview]
Message-ID: <0000000000006aea3f05e3b28443@google.com> (raw)


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

This event has been cancelled with a note:
"Out of office"

GCC Rust hang out
Wednesday 13 Jul 2022 ⋅ 7pm – 7:30pm
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=1658162700000000&usg=AOvVaw3aCEpU8qTt2CP0KDF1i6CX



Hi everyone

This is a regular call for anyone to drop in and talk about gccrs, it  
should suit some people better with this time.

We will reuse our jitsi link: https://meet.jit.si/gccrs-community-call


Thanks

--Phil

Organiser
philip.herron@embecosm.com
philip.herron@embecosm.com

Guests
philip.herron@embecosm.com- organiser
gcc-rust@gcc.gnu.org


~~//~~
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: 18391 bytes --]

[-- Attachment #1.3: Type: text/calendar, Size: 1487 bytes --]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:Europe/London
X-LIC-LOCATION:Europe/London
BEGIN:DAYLIGHT
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19700329T010000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
DTSTART:19701025T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Europe/London:20220713T190000
DTEND;TZID=Europe/London:20220713T193000
DTSTAMP:20220713T164548Z
ORGANIZER;CN=philip.herron@embecosm.com:mailto:philip.herron@embecosm.com
UID:4tl63v6qndrq0l26aisn0b4g5j@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=philip
 .herron@embecosm.com;X-NUM-GUESTS=0:mailto:philip.herron@embecosm.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=gc
 c-rust@gcc.gnu.org;X-NUM-GUESTS=0:mailto:gcc-rust@gcc.gnu.org
RECURRENCE-ID;TZID=Europe/London:20220713T190000
CREATED:20220627T153912Z
DESCRIPTION:Hi everyone\n\nThis is a regular call for anyone to drop in and
  talk about gccrs\, it should suit some people better with this time.\n\nWe
  will reuse our jitsi link: https://meet.jit.si/gccrs-community-call\n \n \
 nThanks\n\n--Phil
LAST-MODIFIED:20220713T164547Z
LOCATION:https://meet.jit.si/gccrs-community-call
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:GCC Rust hang out
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

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

                 reply	other threads:[~2022-07-13 16:45 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=0000000000006aea3f05e3b28443@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).