From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: CHERNIAEV ANDREI <dungeonlords789@naver.com>
Cc: <buildroot@buildroot.org>
Subject: Re: [Buildroot] [Feature request] Find all non-existent config options by CI/CD
Date: Tue, 29 Oct 2024 12:19:08 +0100 [thread overview]
Message-ID: <20241029121908.604a3074@windsurf> (raw)
In-Reply-To: <d6269fa3c64d831751c6ce37d105895@cweb002.nm>
Hello Andrei,
On Tue, 29 Oct 2024 15:38:26 +0900
CHERNIAEV ANDREI <dungeonlords789@naver.com> wrote:
> As [you
> know](https://gitlab.com/buildroot.org/buildroot/-/issues/57) buildroot contains some amount of non-existent BR2_ config options. I suggest to discuss should we make script to automatically detect all bad BR2_ and how to integrate it to CI/CD. In my point of view we also should detect legacy config options which are not marked as "legacy".
> Why I can't make such script? Because I don't know how to get a list
> of all non-legacy BR2_ config options
>
> P.S. Let's
> use https://gitlab.com/buildroot.org/buildroot/-/issues to discuss about new feature!
We already have such a check in check-package, but it checks Config.in
and .mk files, not random documentation indeed.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-29 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 6:38 [Buildroot] [Feature request] Find all non-existent config options by CI/CD CHERNIAEV ANDREI
2024-10-29 11:19 ` Thomas Petazzoni via buildroot [this message]
2024-10-29 11:57 ` CHERNIAEV ANDREI
2024-10-29 16:04 ` Thomas Petazzoni via buildroot
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=20241029121908.604a3074@windsurf \
--to=buildroot@buildroot.org \
--cc=dungeonlords789@naver.com \
--cc=thomas.petazzoni@bootlin.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 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.