From: Julien Olivain <ju.o@free.fr>
To: buildroot@buildroot.org
Cc: Julien Olivain <ju.o@free.fr>,
Etienne Carriere <etienne.carriere@linaro.org>
Subject: [Buildroot] [PATCH 1/1] DEVELOPERS: remove entry for optee-benchmark
Date: Mon, 8 May 2023 20:18:50 +0200 [thread overview]
Message-ID: <20230508181850.21256-1-ju.o@free.fr> (raw)
optee-benchmark package was removed in commit cf39b596e7
("package/optee-benchmark: remove deprecated package") but forgot to
remove the associated DEVELOPERS file entry.
Using the get-developers script on any file generates a warning,
for example:
utils/get-developers DEVELOPERS
WARNING: 'package/optee-benchmark/' doesn't match any file, line 865
git send-email --to buildroot@buildroot.org
This commit fixes the issue by removing the entry.
Cc: Etienne Carriere <etienne.carriere@linaro.org>
Signed-off-by: Julien Olivain <ju.o@free.fr>
---
DEVELOPERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/DEVELOPERS b/DEVELOPERS
index 5658dfa14b..efb2907d1b 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -862,7 +862,6 @@ F: package/python-kiwisolver/
N: Etienne Carriere <etienne.carriere@linaro.org>
F: boot/optee-os/
-F: package/optee-benchmark/
F: package/optee-client/
F: package/optee-examples/
F: package/optee-test/
--
2.40.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-05-08 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 18:18 Julien Olivain [this message]
2023-05-08 18:22 ` [Buildroot] [PATCH 1/1] DEVELOPERS: remove entry for optee-benchmark Yann E. MORIN
2023-05-09 7:14 ` Etienne Carriere
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=20230508181850.21256-1-ju.o@free.fr \
--to=ju.o@free.fr \
--cc=buildroot@buildroot.org \
--cc=etienne.carriere@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.