From: Richard Purdie <rpurdie@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: RFC: Undocumented Recipe Variables Script
Date: Tue, 07 Dec 2010 22:38:50 +0000 [thread overview]
Message-ID: <1291761530.1554.169.camel@rex> (raw)
In-Reply-To: <4CFEB16A.1010507@linux.intel.com>
On Tue, 2010-12-07 at 14:12 -0800, Darren Hart wrote:
> I whipped up a script to find variables in recipes
> and determine if they have been documented.
[...]
> ALTERNATIVE_LINK
> ALTERNATIVE_LINKS
> ALTERNATIVE_NAME
> ALTERNATIVE_PATH
> ALTERNATIVE_PRIORITY
yet if I look at:
http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html#ref-classes-update-alternatives
these ones are.
There is a lot of noise in that script but its probably worth a pass
over the output to hint as to what we need to document.
Cheers,
Richard
next prev parent reply other threads:[~2010-12-07 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 22:12 RFC: Undocumented Recipe Variables Script Darren Hart
2010-12-07 22:38 ` Richard Purdie [this message]
2010-12-07 22:57 ` Darren Hart
2010-12-08 1:27 ` Darren Hart
2010-12-09 13:53 ` Richard Purdie
2010-12-10 19:10 ` Darren Hart
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=1291761530.1554.169.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
/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