From: Philip Balister <philip@balister.org>
To: "Osier-mixon, Jeffrey" <jeffrey.osier-mixon@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Yocto usability questions
Date: Fri, 18 Nov 2011 17:32:48 -0500 [thread overview]
Message-ID: <4EC6DD10.5070702@balister.org> (raw)
In-Reply-To: <CALZ2gZVebXJ6+89O8MHkGgJB=bsSrPusG7x=7Rj=MmpWrnyE1Q@mail.gmail.com>
On 11/18/2011 04:31 PM, Osier-mixon, Jeffrey wrote:
> I have created a Cookbook page on the wiki at
> https://wiki.yoctoproject.org/wiki/Cookbook
>
> If you have tested procedures that work with the Yocto Project, please add
> them to this page.
We need to be really carefully to make sure wiki pages do not get
orphaned. Bad information on wiki's can also be a source of confusion.
I don't hate wiki's, just ones that bitrot.
Philip
next prev parent reply other threads:[~2011-11-18 22:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 22:07 Yocto usability questions Jeff Osier-Mixon
2011-11-16 23:39 ` Mark Hatle
2011-11-17 4:03 ` Ourada, Paul
2011-11-17 7:19 ` Koen Kooi
2011-11-17 13:06 ` Rainer Koenig
2011-11-17 14:25 ` Philip Balister
2011-11-17 21:38 ` Chris Tapp
2011-11-17 22:17 ` Brian Duffy
2011-11-17 23:19 ` Osier-mixon, Jeffrey
2011-11-18 9:40 ` Jack Mitchell
2011-11-18 15:02 ` Ourada, Paul
2011-11-18 15:42 ` Philip Balister
2011-11-18 15:56 ` Gary Thomas
2011-11-18 16:00 ` Philip Balister
2011-11-18 16:04 ` Gary Thomas
2011-11-18 16:56 ` Tom Rini
2011-11-18 16:56 ` Jack Mitchell
2011-11-18 17:20 ` Osier-mixon, Jeffrey
2011-11-18 19:40 ` Jeff Osier-Mixon
2011-11-18 20:12 ` Joshua Lock
2011-11-18 20:54 ` Tom Zanussi
2011-11-18 21:31 ` Osier-mixon, Jeffrey
2011-11-18 21:56 ` Chris Tapp
2011-11-18 22:32 ` Philip Balister [this message]
2011-11-18 22:36 ` Osier-mixon, Jeffrey
2011-11-22 12:52 ` Rainer Koenig
2011-11-22 15:23 ` Tom Zanussi
2011-11-22 16:49 ` Joshua Lock
2011-11-22 21:03 ` Chris Tapp
2011-11-22 22:52 ` Joshua Lock
-- strict thread matches above, loose matches on Subject: below --
2018-12-21 5:16 Prasenjit Mahanti
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=4EC6DD10.5070702@balister.org \
--to=philip@balister.org \
--cc=jeffrey.osier-mixon@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.