From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/6] utils/readme.txt: expand check-package description
Date: Tue, 6 Feb 2024 16:59:45 +0100 [thread overview]
Message-ID: <ZcJXcd5J5UwansD-@landeda> (raw)
In-Reply-To: <20240206105246.1220945-1-buildroot@bubu1.eu>
Marcus, All,
On 2024-02-06 11:52 +0100, Marcus Hoffmann via buildroot spake thusly:
> check-package does a lot more by now than checking .mk and
> Config.in files. Add this to the description.
>
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> utils/readme.txt | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/utils/readme.txt b/utils/readme.txt
> index 3e8833c4ea..d5cda70bfc 100644
> --- a/utils/readme.txt
> +++ b/utils/readme.txt
> @@ -12,8 +12,11 @@ brmake
> nothing.
>
> check-package
> - a script that checks the coding style of a package's Config.in and
> - .mk files, and also tests them for various types of typoes.
> + a script that checks the coding style across the buildroot tree. It
> + checks package's Config.in and .mk files, runs shellcheck for all shell
> + scripts, flake8 for python files, checks for typoes, etc.
> + It checks the .checkpackageignore file if errors should be ignored and
> + errors if there's a file listed that doesn't produce an error.
>
> genrandconfig
> a script that generates a random configuration, used by the autobuilders
> --
> 2.43.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-02-06 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 10:52 [Buildroot] [PATCH 1/6] utils/readme.txt: expand check-package description Marcus Hoffmann via buildroot
2024-02-06 10:52 ` [Buildroot] [PATCH 2/6] utils/readme.txt: document docker-run script Marcus Hoffmann via buildroot
2024-02-06 16:00 ` Yann E. MORIN
2024-02-06 10:52 ` [Buildroot] [PATCH 3/6] docs/website/support.html: document how to join irc channel from matrix Marcus Hoffmann via buildroot
2024-02-06 16:00 ` Yann E. MORIN
2024-02-06 10:52 ` [Buildroot] [PATCH 4/6] docs/website/support.html: document irc channel permission changes Marcus Hoffmann via buildroot
2024-02-06 16:02 ` Yann E. MORIN
2024-02-06 10:52 ` [Buildroot] [PATCH 5/6] docs/manual/contribute.adoc: link to git-send-email.io Marcus Hoffmann via buildroot
2024-02-06 16:03 ` Yann E. MORIN
2024-02-06 10:52 ` [Buildroot] [PATCH 6/6] docs/manual/contribute.adoc: mention sr.ht as an alternative for sending patches Marcus Hoffmann via buildroot
2024-02-06 17:06 ` Yann E. MORIN
2024-02-06 15:59 ` Yann E. MORIN [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=ZcJXcd5J5UwansD-@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox