From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Ali Alnubani <alialnu@nvidia.com>,
Aaron Conole <aconole@redhat.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] [DISCUSS] report format for adding checks to other projects
Date: Thu, 25 Mar 2021 08:17:20 +0000 [thread overview]
Message-ID: <a37c971902dd4853819b507d2a7fb49b@intel.com> (raw)
In-Reply-To: <7927872.xfylkBsRoT@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: 2021年3月25日 16:15
> To: Ali Alnubani <alialnu@nvidia.com>; Aaron Conole <aconole@redhat.com>;
> Tu, Lijuan <lijuan.tu@intel.com>
> Cc: ci@dpdk.org
> Subject: Re: [DISCUSS] report format for adding checks to other projects
>
> 25/03/2021 09:01, Tu, Lijuan:
> > We sent reports to dts project, and it works, e.g.
> > http://patches.dpdk.org/project/dts/patch/1615946979-23566-1-git-send-
> > email-hailinx.xu@intel.com/ but we met another question, which mail
> > address should dts reports send to ?
> > If reports sent to < test-report@dpdk.org>, it will be mixed with dpdk
> > reports, e.g.
> > http://mails.dpdk.org/archives/test-report/2021-March/183128.html
> > And an tag [dpdk-test-report] will be added automatically, it's very confused
> for users.
> > Therefore, Can we have a separated mail address for dts reports?
>
> We need to check which change is required in patchwork processing to have
> multiple test report mailing lists.
> It may take a bit of time. Is it urgent?
No, take your time, thanks
next prev parent reply other threads:[~2021-03-25 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 14:52 Aaron Conole
2021-03-11 15:55 ` Ali Alnubani
2021-03-15 13:56 ` Ali Alnubani
2021-03-25 8:01 ` Tu, Lijuan
2021-03-25 8:14 ` Thomas Monjalon
2021-03-25 8:17 ` Tu, Lijuan [this message]
2021-03-25 16:14 ` Aaron Conole
2021-03-26 1:14 ` Tu, Lijuan
2021-06-07 16:00 ` Thomas Monjalon
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=a37c971902dd4853819b507d2a7fb49b@intel.com \
--to=lijuan.tu@intel.com \
--cc=aconole@redhat.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--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).