From: Ulrich Speidel <ulrich@cs.auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Cc: u.speidel@auckland.ac.nz
Subject: [Starlink] Seminar TODAY on Zoom (on Tonga cable outage and things learned )
Date: Thu, 24 Feb 2022 23:17:55 +1300 [thread overview]
Message-ID: <b8c1678d-ef23-7d39-8882-c9dd040f1d5c@cs.auckland.ac.nz> (raw)
Thanks to everyone who attended today's seminar, especially also to
those who added their comments.
The slides are here:
https://sde.blogs.auckland.ac.nz/2022/02/24/seminar-slides-24-february-2022/
The video recording is here:
https://youtu.be/uZYabj9zzOI
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
next reply other threads:[~2022-02-24 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 10:17 Ulrich Speidel [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-23 13:11 Ulrich Speidel
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
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b8c1678d-ef23-7d39-8882-c9dd040f1d5c@cs.auckland.ac.nz \
--to=ulrich@cs.auckland.ac.nz \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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