From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] lighttpd: adjust Config.in to make check-package happy
Date: Wed, 31 Oct 2018 11:21:09 +0100 [thread overview]
Message-ID: <874ld2ct7u.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181031095117.912A283807@busybox.osuosl.org> (Thomas Petazzoni's message of "Wed, 31 Oct 2018 10:52:14 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=71f4f97d0aebe36c6399822840fe5301a5339b10
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> Commit b9d75c717e01aed474b7567c969236418e87eda8 ("lighttpd: add
> optional pam support") introduced a new Config.in option, but
> check-package was not happy about it:
> package/lighttpd/Config.in:30: should be indented with one tab (http://nightly.buildroot.org/#_config_files)
> package/lighttpd/Config.in:31: should be indented with one tab (http://nightly.buildroot.org/#_config_files)
> package/lighttpd/Config.in:32: attributes order: type, default, depends on, select, help (http://nightly.buildroot.org/#_config_files)
> package/lighttpd/Config.in:32: should be indented with one tab (http://nightly.buildroot.org/#_config_files)
> package/lighttpd/Config.in:33: should be indented with one tab (http://nightly.buildroot.org/#_config_files)
> package/lighttpd/Config.in:34: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in)
> This commit fixes those indentation and ordering issues.
Ups, wonder how that happened. I'll have a look at executing
check-package in a git pre-commit hook.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-10-31 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 9:52 [Buildroot] [git commit] lighttpd: adjust Config.in to make check-package happy Thomas Petazzoni
2018-10-31 10:21 ` Peter Korsgaard [this message]
2018-10-31 10:26 ` Thomas Petazzoni
2018-10-31 10:51 ` Peter Korsgaard
2018-10-31 11:05 ` Peter Korsgaard
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=874ld2ct7u.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