From: Scott Garman <scott.a.garman@intel.com>
To: <yocto@yoctoproject.org>
Subject: Re: bitbake problems when testing pre-built images
Date: Tue, 16 Nov 2010 09:15:36 -0800 [thread overview]
Message-ID: <4CE2BC38.3070603@intel.com> (raw)
In-Reply-To: <4CE14EDD.8060503@ronsgallery.com>
On 11/15/2010 07:16 AM, Ron Olson wrote:
> I second the point about updating the instructions. The whole point of
> the quick start instructions is to let one quickly get their feet on the
> ground. When the documentation is in error, it costs people time and
> frustration. I spent a couple hours working in the dark since this is
> new to me, until I finally found a work-around, when the exercise should
> have taken minutes.
Hi Ron,
I'm sorry to hear that this took up your time in this way, and wanted to
let you know that I'm working with our documentation person to get the
change made to our web site. Unfortunately the person who has access to
make changes on our production server is at a conference this week, so
we're hoping he will be able to make the change in a free moment.
> My suggestion would be that you dry-run documentation such as this,
> using people that have *no* yocto or openembedded background. After
> all, that's the target audience for a 'quick start' page.
Point taken. As a matter of fact, we did do this, but the renaming of
the final images happened literally within a day or two of our public
release, and the bug in the poky-qemu script is due to this renaming. It
just goes to show that even "simple" last-minute changes still need to
be tested. :(
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
prev parent reply other threads:[~2010-11-16 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 20:12 bitbake problems when testing pre-built images Pedro I. Sanchez
2010-11-14 21:20 ` Zhang, Jessica
2010-11-15 0:05 ` Pedro I. Sanchez
2010-11-15 15:16 ` Ron Olson
2010-11-16 17:15 ` Scott Garman [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=4CE2BC38.3070603@intel.com \
--to=scott.a.garman@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.