From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Config.in{,host}: check-package pass
Date: Wed, 14 Feb 2018 21:27:18 +0100 [thread overview]
Message-ID: <20180214212718.6b2f46cd@windsurf.lan> (raw)
In-Reply-To: <20180214050458.32281-1-gael.portay@savoirfairelinux.com>
Hello,
On Wed, 14 Feb 2018 00:04:55 -0500, Ga?l PORTAY wrote:
> Ga?l PORTAY (3):
> package/*/Config.in.host: fix help text check-package warnings
> gconf: Config.in: fix help text wrapping
> pure-ftpd: Config.in: fix help text wrapping
I've applied the patches to the master branch, thanks. However, I'd
like to finally find a solution to validate all those Config.in files
from our .gitlab-ci.yml.
The blocking problem is that package/Config.in and
package/x11r7/Config.in generate a lot of warnings, but we in fact want
to keep them as-is. See the thread at
http://patchwork.ozlabs.org/patch/849882/.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-14 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 5:04 [Buildroot] [PATCH 0/3] Config.in{,host}: check-package pass Gaël PORTAY
2018-02-14 5:04 ` [Buildroot] [PATCH 1/3] package/*/Config.in.host: fix help text check-package warnings Gaël PORTAY
2018-02-14 5:04 ` [Buildroot] [PATCH 2/3] gconf: Config.in: fix help text wrapping Gaël PORTAY
2018-02-14 5:04 ` [Buildroot] [PATCH 3/3] pure-ftpd: " Gaël PORTAY
2018-02-14 17:19 ` Sam Voss
2018-02-14 20:27 ` Thomas Petazzoni [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=20180214212718.6b2f46cd@windsurf.lan \
--to=thomas.petazzoni@bootlin.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.