From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: Re: how much effort is going into updating bitbake user manual?
Date: Tue, 8 Jul 2014 07:48:23 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407080746540.32567@localhost> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237983FB688C@ORSMSX101.amr.corp.intel.com>
On Tue, 8 Jul 2014, Rifenbark, Scott M wrote:
> >From: bitbake-devel-bounces@lists.openembedded.org [mailto:bitbake-
> >devel-bounces@lists.openembedded.org] On Behalf Of Robert P. J. Day
> >Sent: Tuesday, July 08, 2014 4:31 AM
> >To: BitBake developer list
> >Subject: [bitbake-devel] how much effort is going into updating bitbake user
> >manual?
>
> I am working on it in parallel with the YP docs. It is prioritized
> no higher or lower.
ah, gotcha.
> > 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.
> I should have your patches and changes in by end of this week.
great ... i'm pretty sure i'll be done with the bitbake manual in
the next day or two, then move on to the yocto manuals.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-07-08 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 11:31 how much effort is going into updating bitbake user manual? Robert P. J. Day
2014-07-08 11:44 ` Rifenbark, Scott M
2014-07-08 11:48 ` Robert P. J. Day [this message]
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.1407080746540.32567@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-devel@lists.openembedded.org \
--cc=scott.m.rifenbark@intel.com \
/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.