From: jernstfriedman@linuxfoundation.org (jernstfriedman at linuxfoundation.org)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Updated invitation: CIP: F2F - TSC Meeting (Public) @ Sun Oct 21, 2018 4am - 6:30am (PDT) (cip-dev@lists.cip-project.org)
Date: Tue, 16 Oct 2018 21:39:09 +0000 [thread overview]
Message-ID: <000000000000431a3305785f6286@google.com> (raw)
This event has been changed.
Title: CIP: F2F - TSC Meeting (Public) (changed)
Topic: CIP: F2F - TSC Meeting
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/135813681
Or iPhone one-tap :
US: +16699006833,,135813681# or +16465588656,,135813681#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll
Free) or +1 855 880 1246 (Toll Free)
Meeting ID: 135 813 681
International numbers available: https://zoom.us/u/aez3uoLO8E
When: Sun Oct 21, 2018 4am ? 6:30am Pacific Time - Los Angeles (changed)
Where: Edinburgh International Conference Centre, 150 Morrison St,
Edinburgh EH3 8EE, UK - Carrick 2 Suite
Calendar: cip-dev at lists.cip-project.org
Who:
* jernstfriedman at linuxfoundation.org - organizer
* findlay.shearer at intel.com
* cip-members at lists.cip-project.org
* cip-dev at lists.cip-project.org
Event details:
https://www.google.com/calendar/event?action=VIEW&eid=M3V0ZXFoMDRxNW1pZmU2dGFjcXE2bmRxdGwgY2lwLWRldkBsaXN0cy5jaXAtcHJvamVjdC5vcmc&tok=MzQjamVybnN0ZnJpZWRtYW5AbGludXhmb3VuZGF0aW9uLm9yZzVmYjAxNjU4ZmY0MTQ5Y2ExYjAxNzc3ZmJlOTc1NTdiNzcxZDQ4YzI&ctz=America%2FLos_Angeles&hl=en&es=0
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
cip-dev at lists.cip-project.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://www.google.com/calendar/ and control your notification settings for
your entire calendar.
Forwarding this invitation could allow any recipient to modify your RSVP
response. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20181016/392a5d46/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2361 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20181016/392a5d46/attachment.ics>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2408 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20181016/392a5d46/attachment.bin>
reply other threads:[~2018-10-16 21:39 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=000000000000431a3305785f6286@google.com \
--to=jernstfriedman@linuxfoundation.org \
--cc=cip-dev@lists.cip-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.