From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: Brandon Maier <brandon.maier@collins.com>,
Ricardo Martincoski <ricardo.martincoski@datacom.com.br>
Subject: Re: [Buildroot] [PATCH v2 1/3] docs/manual/adding-packages-tips: mention check-package requirements
Date: Sat, 26 Oct 2024 13:40:40 +0200 [thread overview]
Message-ID: <20241026134040.7084d913@windsurf> (raw)
In-Reply-To: <20241009-check-package-requirements-v2-1-df3e7b79788b@collins.com>
On Wed, 09 Oct 2024 14:14:56 +0000
Brandon Maier via buildroot <buildroot@buildroot.org> wrote:
> Call out the requirements to run check-package and mention that Docker
> can be used to run check-package without installing dependencies.
>
> Signed-off-by: Brandon Maier <brandon.maier@collins.com>
> ---
> docs/manual/adding-packages-tips.adoc | 10 ++++++++++
> 1 file changed, 10 insertions(+)
Applied to master after rewording the part that bothered Arnout.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-26 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 14:14 [Buildroot] [PATCH v2 0/3] utils/check-package: make check-package easier to run Brandon Maier via buildroot
2024-10-09 14:14 ` [Buildroot] [PATCH v2 1/3] docs/manual/adding-packages-tips: mention check-package requirements Brandon Maier via buildroot
2024-10-26 11:40 ` Thomas Petazzoni via buildroot [this message]
2024-11-11 10:31 ` Peter Korsgaard
2024-10-09 14:14 ` [Buildroot] [PATCH v2 2/3] utils/check-package: add inline script requirements Brandon Maier via buildroot
2024-10-26 11:41 ` Thomas Petazzoni via buildroot
2024-11-11 10:31 ` Peter Korsgaard
2024-10-09 14:14 ` [Buildroot] [PATCH v2 3/3] docs/manual/adding-packages-tips: mention uv Brandon Maier via buildroot
2024-10-26 11:44 ` Thomas Petazzoni via buildroot
2024-10-28 13:53 ` Brandon Maier 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=20241026134040.7084d913@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=ricardo.martincoski@datacom.com.br \
--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