From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Ricardo Martincoski <ricardo.martincoski@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [master, next, lts] utils/get-developer: fix DEVELOPERS syntax check on GitLab CI
Date: Sun, 24 Jul 2022 11:21:37 +0200 [thread overview]
Message-ID: <20220724112137.3a2c6f36@windsurf> (raw)
In-Reply-To: <263543fd-ec60-fede-a500-2204ec1ffa30@mind.be>
On Sun, 24 Jul 2022 09:45:22 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> > We could catch that in at least two ways:
> > - adding the number of errors and warnings to parse_developers
> > - in the GitLab CI using grep in the stderr from get-developers
>
> Or change parse_developers() to make that warning an error...
Yes, exactly. I think we should consider this issue (file in DEVELOPERS
that doesn't exist in practice) to be a hard error.
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-07-24 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 1:48 [Buildroot] [master, next, lts] utils/get-developer: fix DEVELOPERS syntax check on GitLab CI Ricardo Martincoski
2022-07-23 14:58 ` Thomas Petazzoni via buildroot
2022-07-24 4:31 ` Ricardo Martincoski
2022-07-24 7:45 ` Arnout Vandecappelle
2022-07-24 9:21 ` 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=20220724112137.3a2c6f36@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=ricardo.martincoski@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.