From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: how much effort is going into updating bitbake user manual?
Date: Tue, 8 Jul 2014 07:31:20 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407080725470.32352@localhost> (raw)
i ask since i'm teaching an OE/yocto course in a couple weeks, and i
want to make the bitbake user manual part of the student kit, which is
why i'm currently clawing my way through it, being pedantic and all
and doing lots of (admittedly picky) touchups.
case in point -- there are at least some BB variables that aren't
listed in the glossary, such as PARALLEL_MAKE. i'm making a list of
these, but i know that the yocto project also has a massive reference
manual which includes a variable glossary. so where should i
concentrate my efforts? personally, if something is BB-specific, i'd
rather it go into the BB user manual.
also, what's the timeframe for getting my patches into the repo? the
course isn't til the week of jul 21-24 so there's lots of time for the
patches to be applied, it would just be nice to know that they'll be
incorporated by the time the course starts.
thanks, back to proofreading ...
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-07-08 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 11:31 Robert P. J. Day [this message]
2014-07-08 11:44 ` how much effort is going into updating bitbake user manual? Rifenbark, Scott M
2014-07-08 11:48 ` Robert P. J. Day
2014-07-14 11:24 ` Paul Eggleton
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.1407080725470.32352@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-devel@lists.openembedded.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.