From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: building a hierarchical poky variable glossary, noting what's missing
Date: Wed, 27 Aug 2014 04:14:01 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1408270410350.17600@localhost> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237983FDF114@ORSMSX101.amr.corp.intel.com>
On Tue, 26 Aug 2014, Rifenbark, Scott M wrote:
> Robert,
>
> I can see your link being referenced from the YP ref-manual to
> augment variable descriptions and explanations. Also, your
> compilation could act as another source of information similar to
> the list of "other information" items that currently are shown at
> the front of the dev-manual.
this whole thing will come in fits and spurts, and may even be
redesigned completely if i think of a better way but, for the time
being, if you're bored :-), you can always peruse it from time to
time and note the variables that aren't included either in
documentation.conf or the ref manual and do something about them:
http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary
of course, it's impossible to document *every* variable but in some
cases, it's obvious that some variables deserve documentation.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2014-08-27 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 11:11 building a hierarchical poky variable glossary, noting what's missing Robert P. J. Day
2014-08-26 11:21 ` Rifenbark, Scott M
2014-08-27 8:14 ` Robert P. J. Day [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=alpine.LFD.2.11.1408270410350.17600@localhost \
--to=rpjday@crashcourse.ca \
--cc=scott.m.rifenbark@intel.com \
--cc=yocto@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 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.