From: <scott.m.rifenbark@intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/2] [DOCS] [BUGID# 628] - Added new question and note for Python 2.6 requirement.
Date: Tue, 22 Feb 2011 15:00:44 -0600 [thread overview]
Message-ID: <cover.1298408196.git.scott.m.rifenbark@intel.com> (raw)
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Part of the fix for Bug 628 is to add a note that bitbake requires
python 2.6. I added this note in the Yocto Quick Start Guide
before the example bitbake command
that builds an image.
The other part of the fix for #628 required adding a new question to the
FAQ appendix in the Poky Reference Manual for use of Poky when you do not
have Python 2.6.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: srifenbark/docs
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=srifenbark/docs
Thanks,
<scott.m.rifenbark@intel.com>
---
Scott Rifenbark (2):
documentation/yocto-project-qs/yocto-project-qs.xml: [BUGID# 628] -
Added note about Python 2.6 bitbake requirement
documentation/poky-ref-manual/faq.xml: [BUGID# 628] - Added new
question for Python 2.6 requirement.
documentation/poky-ref-manual/faq.xml | 41 ++++++++++++++++++++
.../yocto-project-qs/yocto-project-qs.xml | 6 +++
2 files changed, 47 insertions(+), 0 deletions(-)
next reply other threads:[~2011-02-22 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:00 scott.m.rifenbark [this message]
2011-02-22 21:00 ` [PATCH 1/2] documentation/yocto-project-qs/yocto-project-qs.xml: [BUGID# 628] - Added note about Python 2.6 bitbake requirement scott.m.rifenbark
2011-02-22 21:00 ` [PATCH 2/2] documentation/poky-ref-manual/faq.xml: [BUGID# 628] - Added new question for Python 2.6 requirement scott.m.rifenbark
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=cover.1298408196.git.scott.m.rifenbark@intel.com \
--to=scott.m.rifenbark@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