From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] utils/get-developers: use Developers.hasfile() where appropriate
Date: Thu, 19 Nov 2020 15:53:53 +0100 [thread overview]
Message-ID: <20201119145354.1175043-3-thomas.petazzoni@bootlin.com> (raw)
In-Reply-To: <20201119145354.1175043-1-thomas.petazzoni@bootlin.com>
Instead of open-coding Developers.hasfile() in utils/get-developers,
use it directly.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
utils/get-developers | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/utils/get-developers b/utils/get-developers
index 750fc556dc..20272ed60b 100755
--- a/utils/get-developers
+++ b/utils/get-developers
@@ -77,9 +77,8 @@ def __main__():
if args.files is not None:
args.files = [os.path.abspath(f) for f in args.files]
for dev in devs:
- for devfile in dev.files:
- commonfiles = [f for f in args.files if f.startswith(devfile)]
- if commonfiles:
+ for f in args.files:
+ if dev.hasfile(f):
print(dev.name)
break
--
2.28.0
next prev parent reply other threads:[~2020-11-19 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 14:53 [Buildroot] [PATCH 1/4] support/scripts/pkg-stats: import cve module only when needed Thomas Petazzoni
2020-11-19 14:53 ` [Buildroot] [PATCH 2/4] support/scripts/pkg-stats: fix Python 3.8 deprecation warning Thomas Petazzoni
2020-11-19 14:53 ` Thomas Petazzoni [this message]
2020-11-20 10:03 ` [Buildroot] [PATCH 3/4] utils/get-developers: use Developers.hasfile() where appropriate Heiko Thiery
2020-11-19 14:53 ` [Buildroot] [PATCH 4/4] utils/getdeveloperlib.py: use relative paths for files Thomas Petazzoni
2020-11-20 10:03 ` Heiko Thiery
2020-11-20 14:14 ` Thomas Petazzoni
2020-11-20 14:26 ` Heiko Thiery
2020-11-20 10:02 ` [Buildroot] [PATCH 1/4] support/scripts/pkg-stats: import cve module only when needed Heiko Thiery
2021-01-17 14:32 ` Thomas Petazzoni
2021-01-19 14:24 ` Peter Korsgaard
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=20201119145354.1175043-3-thomas.petazzoni@bootlin.com \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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