From: Thomas Monjalon <thomas@monjalon.net>
To: Ali Alnubani <alialnu@mellanox.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"jplsek@iol.unh.edu" <jplsek@iol.unh.edu>,
Ori Kam <orika@mellanox.com>
Subject: Re: [dpdk-ci] [PATCH v4] add script to decide best tree match for patches
Date: Fri, 19 Apr 2019 22:39:53 +0200 [thread overview]
Message-ID: <2217950.2hO57oFQ0s@xps> (raw)
In-Reply-To: <20190409161237.28405-1-alialnu@mellanox.com>
09/04/2019 18:12, Ali Alnubani:
> The information provided in the MAINTAINERS file is used to find
> the tree that matches the files changed in patches as follows:
> - For each file, it first tries to find a matching unix shell-style
> pattern. If one was found, it looks for a tree specified in the
> subsection containing the pattern, and that tree is returned.
> If no tree was found in that subsection, the script tries to
> find a tree specified under the name of the section containing
> the pattern.
> - If more than one tree was matched (for multiple files),
> a tree matching the common prefix of all these trees will be
> returned.
> - The main repo 'dpdk' will be returned if no other match was found.
>
> Results can be further improved by adding more information to
> the MAINTAINERS file or by using the subject of the series/patch
> for matching too.
>
> Bugzilla ID: 166
>
> Suggested-by: Thomas Monjalon <thomas@monjalon.net>
> Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
> Signed-off-by: Ori Kam <orika@mellanox.com>
Applied (without unused "import copy"), thanks
prev parent reply other threads:[~2019-04-19 20:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 14:48 [dpdk-ci] [PATCH v2] " Ali Alnubani
2019-02-15 21:28 ` Jeremy Plsek
2019-02-15 23:08 ` Thomas Monjalon
2019-02-17 8:09 ` Ali Alnubani
2019-02-16 16:03 ` [dpdk-ci] [PATCH v3] " Ali Alnubani
2019-04-09 16:12 ` [dpdk-ci] [PATCH v4] " Ali Alnubani
2019-04-18 8:16 ` Ali Alnubani
2019-04-19 16:21 ` Jeremy Plsek
2019-04-19 16:24 ` Thomas Monjalon
2019-04-19 17:33 ` Jeremy Plsek
2019-04-19 17:55 ` Thomas Monjalon
2019-04-19 18:06 ` Jeremy Plsek
2019-04-19 19:41 ` Thomas Monjalon
2019-04-19 19:45 ` Jeremy Plsek
2019-04-19 20:39 ` Thomas Monjalon [this message]
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=2217950.2hO57oFQ0s@xps \
--to=thomas@monjalon.net \
--cc=alialnu@mellanox.com \
--cc=ci@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jplsek@iol.unh.edu \
--cc=orika@mellanox.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).