From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] More maintainers
Date: Sun, 06 Sep 2020 09:43:02 +0200 [thread overview]
Message-ID: <87imcric55.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAFSsvmq4UWvSAhpmJCPt35PagXaZMuHVJenMd8d4oZd7E3KPDA@mail.gmail.com> (Adam Duskett's message of "Sat, 5 Sep 2020 15:25:19 -0700")
>>>>> "Adam" == Adam Duskett <aduskett@gmail.com> writes:
Hi,
Thanks for the constructive input!
> Basic things that could be done with CI/CD that don't take much CPU power and
> would reduce the time spent on each patch:
> - Running check-pkg automatically
I guess you mean check-package?
> - Running basic grammar and spelling checks
I don't know how easy that is to do, given that commit messages often
quote code and/or command output. We can certainly extend check-package
to run the commit message through aspell. What open source utilities are
available for grammar checks?
> - Checking if all recursive dependencies of new packages have been added in
> new Config.in files.
That IMHO very fast becomes complicated with optional dependencies and
patches to existing packages rather than a completely new package, but
if you have a good idea?
> If you want to get complicated a reduction of CPU time/resources could
> also be done with:
> - Having prebuilt docker images or tarballs that have a partially
> complete build
I am not sure how realistic that is given that master (or next) is a
moving target and we would want to test against the current situation?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-09-06 7:43 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
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 [this message]
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=87imcric55.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