From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] manual: board support: add instructions to test defconfig in the official docker
Date: Mon, 14 Feb 2022 08:57:22 +0100 [thread overview]
Message-ID: <20220214085722.330337d9@windsurf> (raw)
In-Reply-To: <20220203235438.610277-1-giulio.benetti@benettiengineering.com>
Hello,
On Fri, 4 Feb 2022 00:54:38 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> +Inside the docker hint:
> +--------------------
> + $ git clone git://git.busybox.net/buildroot
As mentioned on IRC, I think this is not very useful: if you want to
test a new defconfig, or changes to a defconfig, the changes to this
defconfig are not yet in the official repo, so simply cloning the
official repo within the Docker container will not allow you to test
your brand new defconfig.
So as they are, those instructions are in fact not very relevant for
the indicated purpose.
Either the instructions include mounting the local Buildroot copy into
the container, or they instead suggest to use Gitlab CI to validate the
defconfig.
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:[~2022-02-14 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 23:54 [Buildroot] [PATCH] manual: board support: add instructions to test defconfig in the official docker Giulio Benetti
2022-02-12 22:56 ` Luca Ceresoli
2022-02-13 10:39 ` Arnout Vandecappelle
2022-02-13 23:35 ` Giulio Benetti
2022-02-14 12:16 ` Luca Ceresoli
2022-02-15 0:49 ` Giulio Benetti
2022-02-15 2:17 ` Giulio Benetti
2022-02-14 7:57 ` 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=20220214085722.330337d9@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=thomas.de_schampheleire@nokia.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