From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "'ci@dpdk.org'" <ci@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
'Thomas Monjalon' <thomas@monjalon.net>,
"Ye, Xiaolong" <xiaolong.ye@intel.com>
Cc: "Xu, Qian Q" <qian.q.xu@intel.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Yu, PingX" <pingx.yu@intel.com>,
"Chen, BoX C" <box.c.chen@intel.com>,
"Xiao, QimaiX" <qimaix.xiao@intel.com>,
"Zhang, XuemingX" <xuemingx.zhang@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-ci] transfer build servers
Date: Mon, 25 May 2020 04:06:25 +0000 [thread overview]
Message-ID: <efd9340db50c45eb93ed393b62084fb4@intel.com> (raw)
In-Reply-To: <bf2dca503ecc45839efa546496db02a4@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
Hi, all
The dpdk-rc4 has released on 2020/5/25, and there no build issue.
We plan to transfer all the build servers to CD ODC on 2020/5/25,
and the 'daily build report' and 'intel-compilation report in patchwork' will stop from 2020/5/25 - 2020/6/1.
Please kindly let me know if you have any comments.
Regards,
Ma,lihong
From: Ma, LihongX
Sent: Wednesday, May 20, 2020 10:42 AM
To: ci@dpdk.org; test-report@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>; Thomas Monjalon <thomas@monjalon.net>; Ye, Xiaolong <xiaolong.ye@intel.com>
Cc: Xu, Qian Q <qian.q.xu@intel.com>; Tu, Lijuan <lijuan.tu@intel.com>; Peng, Yuan <yuan.peng@intel.com>; Yu, PingX <pingx.yu@intel.com>; Chen, BoX C <box.c.chen@intel.com>; Xiao, QimaiX <qimaix.xiao@intel.com>; Zhang, XuemingX <xuemingx.zhang@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
Subject: transfer build servers
Hi, all
We plan to transfer all the build servers to CD ODC around 2020/5/22 this Friday.
So the 'daily build report' and 'intel-compilation report in patchwork' will stop from 2020/5/22 - 2020/5/29,
Please kindly let me know if you have any comments.
Regards,
Ma,lihong
[-- Attachment #2: Type: text/html, Size: 5373 bytes --]
next prev parent reply other threads:[~2020-05-25 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 2:42 Ma, LihongX
2020-05-25 4:06 ` Ma, LihongX [this message]
2020-06-01 1:27 ` Ma, LihongX
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=efd9340db50c45eb93ed393b62084fb4@intel.com \
--to=lihongx.ma@intel.com \
--cc=box.c.chen@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=lijuan.tu@intel.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=qimaix.xiao@intel.com \
--cc=thomas@monjalon.net \
--cc=xiaolong.ye@intel.com \
--cc=xuemingx.zhang@intel.com \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.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).