From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] test-pkg script can't handle captive portals. etc.
Date: Wed, 1 Mar 2017 21:32:06 +0100 [thread overview]
Message-ID: <20170301213206.7f5746a2@free-electrons.com> (raw)
In-Reply-To: <401e8b88-6d8b-5dea-65c1-dfb0d53cf1ed@mind.be>
Hello,
On Wed, 1 Mar 2017 09:46:28 +0100, Arnout Vandecappelle wrote:
> However, I think it would be much nicer if we could just have the toolchain
> defconfigs inside of Buildroot instead of using this CSV file.
This would actually also solve the problem of having the autobuilders
test master/next/lts branches, since the toolchain defconfigs to test
would be part of Buildroot, and not part of buildroot-test.
There is still the problem of all the special "exclusions" encoded in
the autobuild-run script.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-01 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 20:30 [Buildroot] test-pkg script can't handle captive portals. etc Marcus Hoffmann
2017-03-01 8:46 ` Arnout Vandecappelle
2017-03-01 11:09 ` Marcus Hoffmann
2017-03-01 20:32 ` Thomas Petazzoni [this message]
2017-03-01 20:06 ` Yann E. MORIN
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=20170301213206.7f5746a2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.