From: Ian Rogers <irogers@google.com>
To: linux-perf-users <linux-perf-users@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: June 30th - office hours
Date: Mon, 27 Jun 2022 09:31:15 -0700 [thread overview]
Message-ID: <CAP-5=fUpDdYOcRBBy21cDi=eTov++cKY_E-rnP9++wvopJbijw@mail.gmail.com> (raw)
Hi,
An earlier than of late reminder that there will be another office
hours on June 30th at 2pm GMT*. We should do our usual GSoC
contributor check-ins, please feel free to suggest additional agenda
items!
If you experience problems then my email can be used for Google
hangout messages, I'll try to be on IRC (#perf on irc.oftc.net).
A reminder that the code of conduct is below**:
https://www.kernel.org/doc/html/latest/process/code-of-conduct.html
The Google meet details are here:
Linux Perf Tool - Office Hours
Thursday, June 30 · 7:00 – 8:00am (PDT)
Google Meet joining info
Video call link: https://meet.google.com/goj-quks-ydn
Or dial: (US) +1 301-969-4101 PIN: 374 496 227#
More phone numbers: https://tel.meet/goj-quks-ydn?pin=8067739163431
Notes (ask to be added to see):
https://docs.google.com/document/d/1tQZvJ12czMedpmLLZWS0XILAte97zdR6H_tgC3Ivafs/edit?usp=sharing&resourcekey=0-iV9_8Oc0cSOPl0-NvEYDAA
Thanks,
Ian
*The around the world times I believe are:
China: 10pm
India: 7:30pm
Europe: 4pm
UK: 3pm
US east coast: 10am
Brazil: 11am
US west coast: 7am
**More details from the first office hours are here:
https://lore.kernel.org/linux-perf-users/CAP-5=fWkxtm5-Ebwkh4pzA83prvuAJ5yy6CKQYatdkKWu3Tgeg@mail.gmail.com/
next reply other threads:[~2022-06-27 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 16:31 Ian Rogers [this message]
2022-06-30 6:49 ` June 30th - office hours Ian Rogers
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='CAP-5=fUpDdYOcRBBy21cDi=eTov++cKY_E-rnP9++wvopJbijw@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.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 NNTP newsgroup(s).