From: "Xia, JuanX" <juanx.xia@intel.com>
To: "ci@dpdk.org" <ci@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
NPG SW Core Tools PRC <npg.sw.core.tools.prc@intel.com>,
DPDK_SW_ENG <dpdk_sw_eng@intel.com>
Subject: [dpdk-ci] daily build system will be offline from 1th Oct to 7th Oct
Date: Sat, 29 Sep 2018 08:16:22 +0000 [thread overview]
Message-ID: <B1354E083F6E0444A180C13487DF824DE30EA6@SHSMSX101.ccr.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
Hi All,
Intel daily build system (build on master tree) will be offline from 1th Oct to 7th Oct due to our lab out of power.
Per-patch set system will be offline at 7th Oct due to ODC lab out of power. There is no impact from 1th Oct to 6th Oct.
Sorry for any inconvenience.
[-- Attachment #2: Type: text/html, Size: 2699 bytes --]
reply other threads:[~2018-09-29 8:16 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=B1354E083F6E0444A180C13487DF824DE30EA6@SHSMSX101.ccr.corp.intel.com \
--to=juanx.xia@intel.com \
--cc=ci@dpdk.org \
--cc=dpdk_sw_eng@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=npg.sw.core.tools.prc@intel.com \
--cc=thomas@monjalon.net \
/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).