From: Scott Garman <scott.a.garman@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] documentation-audit.sh: Add/fix checks for skipped lines.
Date: Sun, 09 Dec 2012 11:42:11 -0800 [thread overview]
Message-ID: <50C4E993.8050607@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212090736560.4965@oneiric>
On 12/09/2012 04:39 AM, Robert P. J. Day wrote:
>
> Have the script skip:
>
> * "Recipe" lines.
> * Lines with 11 "=", not 12.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Yeah, I haven't run this script since we switched to the knotty2
interface. If you've tested this, I'm okay with the changes.
Scott
>
> ---
>
> if scott wants to adjust this differently, it's all his.
>
> diff --git a/scripts/contrib/documentation-audit.sh b/scripts/contrib/documentation-audit.sh
> index a2c4586..2144aac 100755
> --- a/scripts/contrib/documentation-audit.sh
> +++ b/scripts/contrib/documentation-audit.sh
> @@ -30,9 +30,10 @@ echo " you'll get false positives. For example, LICENSE_FLAGS_WHITELIST = \"Com
>
> for pkg in `bitbake -s | awk '{ print \$1 }'`; do
> if [[ "$pkg" == "Loading" || "$pkg" == "Loaded" ||
> + "$pkg" == "Recipe" ||
> "$pkg" == "Parsing" || "$pkg" == "Package" ||
> "$pkg" == "NOTE:" || "$pkg" == "WARNING:" ||
> - "$pkg" == "done." || "$pkg" == "============" ]]
> + "$pkg" == "done." || "$pkg" == "===========" ]]
> then
> # Skip initial bitbake output
> continue
>
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-12-09 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 12:39 [PATCH] documentation-audit.sh: Add/fix checks for skipped lines Robert P. J. Day
2012-12-09 19:42 ` Scott Garman [this message]
2012-12-09 19:44 ` Robert P. J. Day
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=50C4E993.8050607@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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