From: Thomas Monjalon <thomas@monjalon.net>
To: "Wei, FangfangX" <fangfangx.wei@intel.com>
Cc: ci@dpdk.org, "Xu, Qian Q" <qian.q.xu@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>,
"Liu, Yuanhan" <yuanhan.liu@intel.com>
Subject: Re: [dpdk-ci] script to determine target repo (was DPDK Lab)
Date: Tue, 25 Apr 2017 08:48:15 +0200 [thread overview]
Message-ID: <4315943.oXb2AriWLG@xps> (raw)
In-Reply-To: <067B569323FEB248B5CB480E1954F4346EA4B2E8@SHSMSX101.ccr.corp.intel.com>
Hi,
25/04/2017 08:37, Wei, FangfangX:
> Hi Thomas,
> Another question need your help: How I can auto-filter the patchset which include some patches?
> Currently we filter the patchset with the format 'Message-Id: <([0-9-]+)-git-send-email-.*@.*>' in per-patch build testing system. But I find that there are some different format about the message-id, such as " 20170420072402.38106-5-aik@ozlabs.ru", "1492658865-30077-1-git-send-email-wei.zhao1@intel.com", "20170209165959.28082-3-benjamin.walker@intel.com", " 3da244231b6868ccc3e70d91dc277df39a3695bd.1481592081.git.mirq-linux@rere.qmqm.pl" and etc.
In the dpdk-ci repo, there is a script tools/filter-patch-email.sh.
next prev parent reply other threads:[~2017-04-25 6:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26FA93C7ED1EAA44AB77D62FBE1D27BA722C837C@IRSMSX108.ger.corp.intel.com>
[not found] ` <HE1PR0501MB21370D6ACD0931D36925D085BD0D0@HE1PR0501MB2137.eurprd05.prod.outlook.com>
[not found] ` <82F45D86ADE5454A95A89742C8D1410E3B5BA2BB@shsmsx102.ccr.corp.intel.com>
[not found] ` <1564461.MHdNEdeViC@xps13>
2017-04-13 5:25 ` [dpdk-ci] DPDK Lab Xu, Qian Q
2017-04-13 6:46 ` [dpdk-ci] script to determine target repo (was DPDK Lab) Thomas Monjalon
2017-04-25 6:23 ` Xu, Qian Q
2017-04-25 6:24 ` Xu, Qian Q
2017-04-25 6:37 ` Wei, FangfangX
2017-04-25 6:41 ` Wei, FangfangX
2017-04-25 6:48 ` Thomas Monjalon [this message]
2017-04-25 6:50 ` Thomas Monjalon
2017-06-21 7:45 ` Wei, FangfangX
2017-06-21 8:20 ` Richardson, Bruce
2017-06-21 8:33 ` Thomas Monjalon
2017-06-23 8:43 ` Xu, Qian Q
2017-06-23 9:30 ` Richardson, Bruce
2017-06-26 3:47 ` Xu, Qian Q
2017-06-26 6:23 ` Jerin Jacob
2017-06-26 13:26 ` Xu, Qian Q
2017-06-30 8:41 ` Wei, FangfangX
2017-06-30 9:22 ` Thomas Monjalon
2017-04-13 8:24 ` [dpdk-ci] DPDK Lab Richardson, Bruce
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=4315943.oXb2AriWLG@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=fangfangx.wei@intel.com \
--cc=qian.q.xu@intel.com \
--cc=tim.odriscoll@intel.com \
--cc=yuanhan.liu@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).