From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] More maintainers
Date: Fri, 04 Sep 2020 21:05:42 +0200 [thread overview]
Message-ID: <87ft7xmkft.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAOf5uwmN0e4CoO6FyQ8UEGGudy1zSTm_GjRyJhHTCgWqmL5rHw@mail.gmail.com> (Michael Nazzareno Trimarchi's message of "Fri, 4 Sep 2020 20:12:49 +0200")
>>>>> "Michael" == Michael Nazzareno Trimarchi <michael@amarulasolutions.com> writes:
Hi,
>> And why wouldn't you be able to do the same with the email based setup
>> today? With tools like snowpatch (https://github.com/ruscur/snowpatch) or
>> some basic scripting around the patchwork REST API nicely allows you to
>> run (command line :P) tools whenever new patches are posted.
>>
> I think that we should explore using snowpatch. Problem is to have a setup
> and some machines that can run the CI. Is there a cost to have this running?
Yes, it would need to run somewhere. Given the machine ressources spent
on the autobuilders and defconfigs/runtime tests already, we can probably
find ressources for that as well. Perhaps osuosl can help?
But before we can do that we would need to figure out exactly what tests
to do and what to report back to the submitter, E.G. running
check-package is trivial, but figuring out what build tests or what
runtime tests to run less so.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-09-04 19:05 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 17:34 [Buildroot] More maintainers Adam Duskett
2020-08-27 19:35 ` Angelo Compagnucci
2020-08-27 20:39 ` Thomas Petazzoni
2020-08-29 9:50 ` Yann E. MORIN
2020-09-02 17:53 ` Adam Duskett
2020-09-02 20:08 ` Arnout Vandecappelle
2020-09-02 20:11 ` Adam Duskett
2020-09-02 21:51 ` Christian Stewart
2020-09-03 15:44 ` Avraham Shukron
2020-09-03 16:24 ` Thomas Petazzoni
2020-09-03 16:44 ` Angelo Compagnucci
2020-09-03 17:29 ` Adam Duskett
2020-09-04 8:31 ` Nicolas Cavallari
2020-09-04 17:39 ` Peter Korsgaard
2020-09-04 18:12 ` Michael Nazzareno Trimarchi
2020-09-04 19:05 ` Peter Korsgaard [this message]
2020-09-04 19:36 ` Angelo Compagnucci
2020-09-04 21:10 ` Peter Korsgaard
2020-09-05 4:52 ` Christian Stewart
2020-09-05 6:44 ` Peter Korsgaard
2020-09-05 16:20 ` Adam Duskett
2020-09-05 17:25 ` Peter Korsgaard
2020-09-05 19:16 ` Thomas Petazzoni
2020-09-05 20:10 ` Angelo Compagnucci
2020-09-05 20:38 ` Thomas Petazzoni
2020-09-05 20:55 ` Angelo Compagnucci
2020-09-05 21:04 ` Thomas Petazzoni
2020-09-05 21:34 ` Angelo Compagnucci
2020-09-05 22:25 ` Adam Duskett
2020-09-06 7:43 ` Peter Korsgaard
2020-09-06 7:58 ` Yegor Yefremov
2020-09-07 15:02 ` Heiko Thiery
2020-09-07 15:20 ` Thomas Petazzoni
2020-09-07 15:43 ` Heiko Thiery
2020-09-10 22:30 ` Christian Stewart
2020-09-05 20:25 ` Yann E. MORIN
2020-09-05 20:54 ` Yann E. MORIN
2020-09-05 18:59 ` Alexander Dahl
2020-09-05 19:17 ` Peter Korsgaard
2020-09-05 20:06 ` Christian Stewart
2020-09-04 17:30 ` James Hilliard
2020-09-03 16:28 ` Angelo Compagnucci
2020-09-04 18:52 ` Peter Korsgaard
2020-09-03 18:39 ` Christian Stewart
2020-09-07 15:57 ` Michael Nosthoff
2020-09-07 18:35 ` Alexander Dahl
2020-09-09 6:14 ` Peter Korsgaard
2020-09-05 13:06 ` [Buildroot] More maintainers: a live discussion ? Thomas Petazzoni
2020-09-07 8:02 ` Thomas Petazzoni
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=87ft7xmkft.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox