All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Yocto usability questions
Date: Tue, 22 Nov 2011 14:52:06 -0800	[thread overview]
Message-ID: <4ECC2796.6040900@linux.intel.com> (raw)
In-Reply-To: <723A693C-B023-4E36-9338-CD0F8B88452B@keylevel.com>



On 22/11/11 13:03, Chris Tapp wrote:
> Hi Joshua,
>
> On 22 Nov 2011, at 16:49, Joshua Lock wrote:
>> On 22/11/11 04:52, Rainer Koenig wrote:
>>> Hi Tom,
>>>
>>> On 18.11.2011 21:54, Tom Zanussi wrote:
>>>
>>>> I'd be happy to work with anyone who wants to in helping getting
>>>> something like that started, whether it be a variation on the above, or
>>>> something from scratch, whatever.
>>>
>>> I just added a few FAQ entries to the wiki. I used the questions from
>>> Chris Tapp and what came to my mind recently. And I used categories, so
>>> that there is a hope for a sort of workflow. See
>>>
>>> https://wiki.yoctoproject.org/wiki/Category:FAQ
>>
>> Any feedback from you, Chris or anyone else as to whether the
>> documentation I linked to for some of those questions is sufficient? If
>> not I can work on enhancing that documentation.
>
>
> Yes, that looks good to me. I've already started a draft for the startup
> scripts FAQ under the https://wiki.yoctoproject.org/wiki/Cookbook page
> that Jeffrey started at the end of last week. Where should it go?

I like the format Rainer came up with, I'd go with that for now.

>
> PS Sorry it's taken a while to reply - Yocto is the night job, not the
> day one ;-)
>

No problem at all, I just wanted to make sure I'd provided enough 
information to keep you going before I ran off for a long turkey break :-)

Joshua
-- 
Joshua Lock
         Yocto Project "Johannes factotum"
         Intel Open Source Technology Centre


  reply	other threads:[~2011-11-22 22:52 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
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 [this message]
  -- 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=4ECC2796.6040900@linux.intel.com \
    --to=josh@linux.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.