From: Jeremy Plsek <jplsek@iol.unh.edu>
To: ci@dpdk.org
Cc: dpdklab@iol.unh.edu
Subject: Re: [dpdk-ci] UNH IOL CI downtime
Date: Tue, 26 Nov 2019 17:42:26 -0500 [thread overview]
Message-ID: <CA+xUZB5m_cK-BR4QzOzOMfa_zCjzu9vpGR4rwzWy_aGGvDm67A@mail.gmail.com> (raw)
In-Reply-To: <CA+xUZB5oeY=pLQT_Onk5Z0d51g0UGb3jiP85oh5hQ0QLnsAp7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
Network changes are done. Let me know if there are any connection issues
(vpn, etc).
Thanks!
On Mon, Nov 25, 2019 at 6:22 PM Jeremy Plsek <jplsek@iol.unh.edu> wrote:
> Hi,
>
> The UNH IOL will be doing some network maintenance tomorrow afternoon,
> which may affect our group. The CI may be down during this time.
>
> The CI will catch up on its own when we come back online.
>
> The changes should be done by tomorrow night.
>
> Thanks
>
--
Jeremy Plsek
UNH InterOperability Laboratory
[-- Attachment #2: Type: text/html, Size: 1242 bytes --]
prev parent reply other threads:[~2019-11-26 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 23:22 Jeremy Plsek
2019-11-26 22:42 ` Jeremy Plsek [this message]
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=CA+xUZB5m_cK-BR4QzOzOMfa_zCjzu9vpGR4rwzWy_aGGvDm67A@mail.gmail.com \
--to=jplsek@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dpdklab@iol.unh.edu \
/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).