From: David Lambert <dave@lambsys.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Documentation
Date: Wed, 01 Dec 2010 12:39:15 -0600 [thread overview]
Message-ID: <4CF69653.5000504@lambsys.com> (raw)
In-Reply-To: <20101201180621.GB20482@excalibur.local>
That is indeed the version of documentation that I was reading. To be
more specific, one of the subjects I was attempting to look up was how
to specialize a recipe using "amend.inc". I do not see any documentation
on this subject.
Regards,
Dave.
On 12/01/2010 12:06 PM, Stefan Schmidt wrote:
> Hello.
>
> On Wed, 2010-12-01 at 12:00, David Lambert wrote:
>> I have been reading a copy of the OpenEmbedded User Manual (latest
>> copyright 2009). In this document I find that there are numerous
>> sections which are stubs and/or are incomplete. As a newcomer to the
>> world of OpenEmbedded what other documents are suggested for
>> reading? Also, is there a later version of this manual?
> My glassball is in repair so I can't see what manual you have and if a newer one
> is available. Adding some kind of date string would help us here.
>
> The user manual is build directly from the sources and should be always up to
> date here:
> http://docs.openembedded.org/usermanual/usermanual.html
>
> regards
> Stefan Schmidt
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2010-12-01 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 18:00 Documentation David Lambert
2010-12-01 18:06 ` Documentation Stefan Schmidt
2010-12-01 18:39 ` David Lambert [this message]
2010-12-01 18:54 ` Documentation Stefan Schmidt
2010-12-01 22:46 ` Documentation Robert Foerster
2010-12-02 20:37 ` Documentation David Lambert
2010-12-02 20:52 ` Documentation Robert Foerster
2010-12-03 7:35 ` Documentation Christophe Aeschlimann
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=4CF69653.5000504@lambsys.com \
--to=dave@lambsys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox