From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH buildroot-test 1/1] scripts/autobuild-run: add support for --branch option
Date: Wed, 8 Feb 2023 16:15:27 +0100 [thread overview]
Message-ID: <20230208161527.31a28b3b@windsurf> (raw)
In-Reply-To: <20220607231211.533086-1-james.hilliard1@gmail.com>
On Tue, 7 Jun 2022 17:12:11 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> In some cases it only makes sense to run tests against a specific
> branch, such as when testing new genrandconfig flags.
>
> Add a config option to override the branch selection.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> scripts/autobuild-run | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
We looked at this with Arnout, and we don't really see what this would
be needed, and actually it could be annoying to have people test
"random" branches. If you need extensions to genrandconfig, then the
autobuild-run script should be backward compatible with older versions
of genrandconfig to be able to support older branches for a certain
while.
Thanks!
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:[~2023-02-08 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 23:12 [Buildroot] [PATCH buildroot-test 1/1] scripts/autobuild-run: add support for --branch option James Hilliard
2023-02-08 15:15 ` Thomas Petazzoni via buildroot [this message]
2023-02-08 16:46 ` James Hilliard
2023-02-09 20:19 ` Arnout Vandecappelle
2023-02-09 20:32 ` James Hilliard
2023-02-09 20:44 ` Arnout Vandecappelle
2023-02-09 21:42 ` James Hilliard
2023-02-15 20:19 ` Arnout Vandecappelle
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=20230208161527.31a28b3b@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.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.