From: Geoffrey Wossum <geoffrey@pager.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: New OE user question
Date: Mon, 31 Mar 2008 11:01:38 -0500 [thread overview]
Message-ID: <200803311101.39141.geoffrey@pager.net> (raw)
In-Reply-To: <200803310907.56781.e.robertson.svg@gmail.com>
On Monday 31 March 2008 09:07:48 am E Robertson wrote:
> Hi All,
>
> I'm brand new to OE and I've been following the documentation steps along
> the way. I notice the documentation is either missing sections or not clear
> and as I learn how to use this tool, I would like to update the
> documentation sections. It's probably the least I could do as I figure out
> how this works. I'm referirng to the user manual wiki. Both configuring and
> building sections are missing clarity.
> Who is responsible for the manual and how do I submit info to the sections?
May not help you with your current issue, but I've discovered that the Poky
handbook is a better source of OpenEmbedded info than the OpenEmbedded
documetation.
http://www.pokylinux.org/doc/poky-handbook.html
---
Geoffrey
next prev parent reply other threads:[~2008-03-31 16:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 14:07 New OE user question E Robertson
2008-03-31 15:33 ` Cliff Brake
2008-03-31 16:19 ` E Robertson
2008-03-31 17:12 ` Cliff Brake
2008-03-31 17:09 ` E Robertson
2008-03-31 17:33 ` Cliff Brake
2008-03-31 15:44 ` Leon Woestenberg
2008-03-31 16:12 ` Koen Kooi
2008-03-31 16:26 ` E Robertson
2008-03-31 16:34 ` Geoffrey Wossum
2008-03-31 17:47 ` Leon Woestenberg
2008-04-01 5:45 ` Ulf Samuelsson
2008-03-31 16:01 ` Geoffrey Wossum [this message]
2008-04-01 6:40 ` OE Manual: License change? (was: Re: New OE user question) Marcin Juszkiewicz
2008-04-01 11:00 ` OE Manual: License change? Jeremy Lainé
2008-04-01 13:08 ` Leon Woestenberg
2008-04-01 15:27 ` Marcin Juszkiewicz
2008-04-01 15:54 ` Robert Schuster
2008-04-01 20:48 ` Richard Purdie
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=200803311101.39141.geoffrey@pager.net \
--to=geoffrey@pager.net \
--cc=openembedded-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.