All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: yocto@yoctoproject.org
Subject: Re: <rant>the current yocto FAQ is pretty much valueless</rant>
Date: Wed, 27 Jun 2012 17:14:12 -0400	[thread overview]
Message-ID: <4FEB77A4.3000204@balister.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1206261252060.5948@oneiric>

On 06/26/2012 12:53 PM, Robert P. J. Day wrote:
> On Tue, 26 Jun 2012, Tomas Frydrych wrote:
>
>> Kooen's cheeky point is worth keeping in mind though; the Yocto
>> naming semantics is not very helpful ;-) Specifically most of the
>> questions being asked on the Yocto list are about Poky, not Yocto,
>> followed by questions about meta-yocto, not Yocto-project. Many of
>> the questions being asked on the list are readily answered by
>> googling for 'Poky Manual', but clearly very few people understand
>> the Yocto project semantics enough to do this ...
>
>    and if you want major industry players to take yocto seriously, the
> last thing you want to do is answer their heartfelt pleas for
> assistance with, "i'm sorry, that's technically not a yocto question,
> you should try another mailing list."
>
>    even if you're technically correct, that sort of conversation is not
> going to end well.

The number one question I get asked about the Yocto Project (this is 
from an audience of people in the software radio area) is how the Yocto 
project relates to OpenEmbedded (and sometimes Angstrom).

Having a realy good answer to this on the FAQ would be awesome.

Philip

PS: Yes, I know this thread is a few days old. I'm on vacation, sue me :)



  parent reply	other threads:[~2012-06-27 21:14 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26  9:09 <rant>the current yocto FAQ is pretty much valueless</rant> Robert P. J. Day
2012-06-26  9:35 ` Jack Mitchell
2012-06-26  9:55 ` Tomas Frydrych
2012-06-26 10:09 ` Paul Eggleton
2012-06-26 10:18   ` Robert P. J. Day
2012-06-26 15:46   ` Darren Hart
2012-06-26 16:06     ` Paul Eggleton
2012-06-26 16:38       ` Tomas Frydrych
2012-06-26 16:53         ` Robert P. J. Day
2012-06-26 17:18           ` Tomas Frydrych
2012-06-26 17:59             ` Brian Duffy
2012-06-27  9:39               ` Tomas Frydrych
2012-06-26 18:52             ` Tim Bird
2012-06-27  9:09               ` Tomas Frydrych
2012-06-27 14:59                 ` Koen Kooi
2012-06-27 16:43                   ` Chris Hallinan
2012-06-27 17:27                     ` Koen Kooi
2012-06-27 20:14                   ` Tomas Frydrych
2012-06-27 21:58                     ` Koen Kooi
2012-06-28  7:44                       ` Tomas Frydrych
2012-07-01 16:23                         ` Philip Balister
2012-06-27 21:14           ` Philip Balister [this message]
2012-06-27 21:51           ` Philip Balister
2012-06-26 11:29 ` Koen Kooi
2012-06-26 14:40   ` Rifenbark, Scott M
2012-06-26 15:45     ` Robert P. J. Day
2012-06-26 15:50       ` Rifenbark, Scott M
2012-06-26 16:18       ` Paul Eggleton
2012-06-26 16:26         ` Robert P. J. Day
2012-06-26 16:33           ` Paul Eggleton
2012-06-26 16:51             ` Robert P. J. Day
2012-06-26 17:02               ` Paul Eggleton
2012-06-26 17:05                 ` Robert P. J. Day
2012-06-26 17:09                   ` Paul Eggleton
2012-06-26 17:14                     ` Robert P. J. Day
2012-06-26 17:08                 ` Rifenbark, Scott M
2012-06-26 17:12                   ` Robert P. J. Day
2012-06-27 16:42   ` Jeff Osier-Mixon

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=4FEB77A4.3000204@balister.org \
    --to=philip@balister.org \
    --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.