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 17:04:17 +0100 [thread overview]
Message-ID: <20241029170417.435fd8ad@windsurf> (raw)
In-Reply-To: <58534f324981edb8a3a348673b5ba25e@cweb016.nm>
Hello,
On Tue, 29 Oct 2024 20:57:07 +0900
CHERNIAEV ANDREI <dungeonlords789@naver.com> wrote:
> Why you call the officially part of buildroot documentation as
> "random documentation"? Is file "/support/kconfig/README.buildroot"
> or "buildroot/blob/master/board/qemu/x86/readme.txt" also "random
> documentation"? So if any file from buildroot repo is not Config.in
> or .mk then buildroot doesn't plan to check it?
For now, check-package is only capable of verifying the coding style of
Config.in, .hash files, .mk files. At this point, I don't expect it to
ever be capable of scanning/validating *.txt files, as their content
can be quite arbitrary.
Of course, you are welcome to develop improvements in this area if you
feel like it should be improved.
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
prev parent reply other threads:[~2024-10-29 16:04 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
2024-10-29 11:57 ` CHERNIAEV ANDREI
2024-10-29 16:04 ` Thomas Petazzoni via buildroot [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=20241029170417.435fd8ad@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox