From: Thomas Monjalon <thomas@monjalon.net>
To: ci@dpdk.org
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: Re: [dpdk-ci] Minutes of DPDK Lab Meeting, November 6th
Date: Tue, 06 Nov 2018 21:32:52 +0100 [thread overview]
Message-ID: <1585164.mQCs1bNvsR@xps> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77AC982@IRSMSX108.ger.corp.intel.com>
06/11/2018 16:19, O'Driscoll, Tim:
> Patchwork Integration:
> - To make the results more visible, and to ensure that developers and maintainers act on them, we agreed that results should be integrated into Patchwork, similar to the way that build tests are handled. Jeremy will review the scripts in the ci repository to determine required email format etc. Ali can help with any issues.
The script to use is:
http://git.dpdk.org/tools/dpdk-ci/tree/tools/send-patch-report.sh
The sender must be whitelisted in order to appear in patchwork.
next prev parent reply other threads:[~2018-11-06 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 15:19 O'Driscoll, Tim
2018-11-06 20:32 ` Thomas Monjalon [this message]
2018-11-07 5:29 ` Tu, Lijuan
2018-11-07 10:01 ` O'Driscoll, Tim
2018-11-08 12:59 ` Ferruh Yigit
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=1585164.mQCs1bNvsR@xps \
--to=thomas@monjalon.net \
--cc=ci@dpdk.org \
--cc=tim.odriscoll@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).