From: Patrick Robb <probb@iol.unh.edu>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
"Paul Szczepanek" <Paul.Szczepanek@arm.com>,
"Luca Vizzarro" <Luca.Vizzarro@arm.com>,
"Yoan Picchi" <yoan.picchi@foss.arm.com>,
"Jeremy Spewock" <jspewock@iol.unh.edu>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
getelson@nvidia.com
Cc: ci@dpdk.org
Subject: Regular DTS meeting scheduling
Date: Fri, 22 Dec 2023 13:33:30 -0500 [thread overview]
Message-ID: <CAJvnSUBrKci_f3A1G47bEEtnTKxEXq26+a0wd_MTKZDnkzZYmw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Hello all DTS interested people,
I'm looking to find a good timeslot for having DTS sync calls this Spring.
Obviously we want to do it on the off weeks from the CI meetings, and we
want to do it in the morning USA time so that it works for EU people too.
Right now the timeslots I'm looking at are:
14:00-15:00 UTC Mondays
15:00-16:00 UTC Mondays
14:00-15:00 UTC Wednesdays
15:00-16:00 UTC Wednesdays
All else being equal, Wednesdays are probably best, as it allows for better
spacing between CI meetings, but we'll do whatever works for the most
people. Please feel free to indicate your availability!
Best,
Patrick
[-- Attachment #2: Type: text/html, Size: 829 bytes --]
next reply other threads:[~2023-12-22 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 18:33 Patrick Robb [this message]
2023-12-22 22:20 ` Thomas Monjalon
2023-12-25 4:43 ` Etelson, Gregory
2024-01-02 9:26 ` Paul Szczepanek
2024-01-02 21:56 ` Honnappa Nagarahalli
2024-01-02 23:08 ` Patrick Robb
2024-01-03 10:55 ` Juraj Linkeš
2024-01-09 14:59 ` Patrick Robb
2024-01-09 15:13 ` Patrick Robb
2024-01-16 23:08 ` Patrick Robb
2024-01-17 15:10 ` Patrick Robb
2024-01-17 15:12 ` Patrick Robb
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=CAJvnSUBrKci_f3A1G47bEEtnTKxEXq26+a0wd_MTKZDnkzZYmw@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=ci@dpdk.org \
--cc=getelson@nvidia.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=thomas@monjalon.net \
--cc=yoan.picchi@foss.arm.com \
/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).